Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754083AbYKXPVp (ORCPT ); Mon, 24 Nov 2008 10:21:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753953AbYKXPU4 (ORCPT ); Mon, 24 Nov 2008 10:20:56 -0500 Received: from mtagate2.uk.ibm.com ([194.196.100.162]:41092 "EHLO mtagate2.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753945AbYKXPUy (ORCPT ); Mon, 24 Nov 2008 10:20:54 -0500 Message-ID: <492AC64E.9080800@fr.ibm.com> Date: Mon, 24 Nov 2008 16:20:46 +0100 From: Daniel Lezcano User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Kay Sievers CC: Linux Kernel Mailing List , Linux Netdev List , Greg KH , David Miller , Linux Containers , "Eric W. Biederman" , Benjamin Thery Subject: Re: [patch 1/1][RFC]Handle uevent per namespace References: <492A86FA.5080804@fr.ibm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 36 Kay Sievers wrote: > On Mon, Nov 24, 2008 at 11:50, Daniel Lezcano 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/