On Fri, Jul 11, 2014 at 10:50:14AM +0200, Uwe Kleine-König wrote:
Olof Johansson pointed out that usually the company name is picked as
namespace prefix to specific properties. So expect "energymicro,location"
but fall back to the previously introduced name "efm32,location".
Cc: Olof Johansson <redacted>
Signed-off-by: Uwe Kleine-König <redacted>
Applied to for-next, thanks! If you think this is better suited in
for-current, let me know.
On Thu, Jul 17, 2014 at 03:40:00PM +0200, Wolfram Sang wrote:
On Fri, Jul 11, 2014 at 10:50:14AM +0200, Uwe Kleine-König wrote:
quoted
Olof Johansson pointed out that usually the company name is picked as
namespace prefix to specific properties. So expect "energymicro,location"
but fall back to the previously introduced name "efm32,location".
Cc: Olof Johansson <redacted>
Signed-off-by: Uwe Kleine-König <redacted>
Applied to for-next, thanks! If you think this is better suited in
for-current, let me know.
I'm not in a hurry. If you take it it's fine for me.
(BTW, I'm not sure i fI understand your branch naming. for-next means
"targeting the next merge window" and for-current means "targeting the
next release"? So for-next currently means 3.17-rc1?)
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |