All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Greg KH <greg@kroah.com>, David Miller <davem@davemloft.net>,
	Linux Containers <containers@lists.osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Benjamin Thery <benjamin.thery@bull.net>
Subject: Re: [patch 1/1][RFC]Handle uevent per namespace
Date: Mon, 24 Nov 2008 16:20:46 +0100	[thread overview]
Message-ID: <492AC64E.9080800@fr.ibm.com> (raw)
In-Reply-To: <ac3eb2510811240714l76b15469lea541bb4badd328@mail.gmail.com>

Kay Sievers wrote:
> On Mon, Nov 24, 2008 at 11:50, Daniel Lezcano <dlezcano@fr.ibm.com> wrote:
> 
>  struct kobject {
>  	const char		*name;
>  	struct list_head	entry;
> @@ -63,6 +65,9 @@ struct kobject {
>  	struct kset		*kset;
>  	struct kobj_type	*ktype;
>  	struct sysfs_dirent	*sd;
> +#ifdef CONFIG_NET
> +	struct net              *net;
> +#endif
>  	struct kref		kref;
>  	unsigned int state_initialized:1;
>  	unsigned int state_in_sysfs:1;
> 
> We cannot do that. Network specific stuff does not belong into
> kobjects. Kobjects are not in any way subsystem specific, and we need
> to keep it that way.

That makes sense :)

Is there a way to follow up from the kobject, the netdev associated with 
it ? I mean in the function kobject_uevent_env, how can I check the 
event is related to a network device and retrieve the struct net_device 
from it ?

Thanks.
  -- Daniel


  reply	other threads:[~2008-11-24 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 10:50 [patch 1/1][RFC]Handle uevent per namespace Daniel Lezcano
2008-11-24 15:14 ` Kay Sievers
2008-11-24 15:20   ` Daniel Lezcano [this message]
2008-11-24 15:31 ` Greg KH
2008-11-24 15:55   ` Daniel Lezcano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=492AC64E.9080800@fr.ibm.com \
    --to=dlezcano@fr.ibm.com \
    --cc=benjamin.thery@bull.net \
    --cc=containers@lists.osdl.org \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.