Thread (67 messages) 67 messages, 5 authors, 2012-09-12

Re: [PATCH v3] can: rename LED trigger name on netdev renames

From: Oliver Hartkopp <socketcan@hartkopp.net>
Date: 2012-09-11 05:42:22
Also in: lkml

On 10.09.2012 22:08, Kurt Van Dijck wrote:
On Mon, Sep 10, 2012 at 09:01:21PM +0200, Oliver Hartkopp wrote:
quoted
quoted
quoted
quoted
+	if (msg == NETDEV_CHANGENAME) {

I do have a second remark.

What about always using the notifiers to name the LED triggers?

Looking into

http://lxr.linux.no/#linux+v3.5.3/include/linux/netdevice.h#L1526

we have NETDEV_CHANGENAME but what about

	NETDEV_REGISTER

???

When changing and updating the LED trigger name always inside the notifier, we
should never run into any locking or race conditions ...

What do you think about this idea?
But the initial name must have been set properly already in that case...

Yes it is.

See register_netdevice()

http://lxr.linux.no/#linux+v3.5.3/net/core/dev.c#L5453


at the end NETDEV_REGISTER is notified:

http://lxr.linux.no/#linux+v3.5.3/net/core/dev.c#L5552

So it would be pretty elegant to create the LED trigger name in the notifier.
This would allow to remove that code at the current init function too.

Regards,
Oliver
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help