From: "Ming Lei" <tom.leiming@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: kay.sievers@vrfy.org, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/ksysfs.c:fix dependence on CONFIG_NET
Date: Wed, 19 Nov 2008 09:25:53 +0800 [thread overview]
Message-ID: <d82e647a0811181725y3a01f9aanca4cf3ca7e8f3081@mail.gmail.com> (raw)
In-Reply-To: <20081118154128.56d1d3ca.akpm@linux-foundation.org>
2008/11/19 Andrew Morton <akpm@linux-foundation.org>:
> On Tue, 18 Nov 2008 15:38:18 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> On Sun, 16 Nov 2008 18:22:09 +0800
>> tom.leiming@gmail.com wrote:
>>
>> > From: Ming Lei <tom.leiming@gmail.com>
>> >
>> > Access to uevent_seqnum and uevent_helper does not need to
>> > depend on CONFIG_NET, so remove it.
>> >
>> > Signed-off-by: Ming Lei <tom.leiming@gmail.com>
>> > ---
>> > kernel/ksysfs.c | 4 ++--
>> > 1 files changed, 2 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/kernel/ksysfs.c b/kernel/ksysfs.c
>> > index 08dd8ed..528dd78 100644
>> > --- a/kernel/ksysfs.c
>> > +++ b/kernel/ksysfs.c
>> > @@ -24,7 +24,7 @@ static struct kobj_attribute _name##_attr = __ATTR_RO(_name)
>> > static struct kobj_attribute _name##_attr = \
>> > __ATTR(_name, 0644, _name##_show, _name##_store)
>> >
>> > -#if defined(CONFIG_HOTPLUG) && defined(CONFIG_NET)
>> > +#if defined(CONFIG_HOTPLUG)
>> > /* current uevent sequence number */
>> > static ssize_t uevent_seqnum_show(struct kobject *kobj,
>> > struct kobj_attribute *attr, char *buf)
>> > @@ -137,7 +137,7 @@ struct kobject *kernel_kobj;
>> > EXPORT_SYMBOL_GPL(kernel_kobj);
>> >
>> > static struct attribute * kernel_attrs[] = {
>> > -#if defined(CONFIG_HOTPLUG) && defined(CONFIG_NET)
>> > +#if defined(CONFIG_HOTPLUG)
>> > &uevent_seqnum_attr.attr,
>> > &uevent_helper_attr.attr,
>> > #endif
>>
>> I think the story here is that uevent uses netlink, and with
>> CONFIG_NET=n, we have no netlink, so that code couldn't do anything
>> anyway.
>>
>
> Or not. Perhaps we can still use uevent_helper in this case?
yes.
>
> (Getting a bit tired of writing people's changelogs for them!)
>
--
Lei Ming
prev parent reply other threads:[~2008-11-19 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 10:22 tom.leiming
2008-11-18 23:38 ` Andrew Morton
2008-11-18 23:41 ` Andrew Morton
2008-11-19 1:25 ` Ming Lei [this message]
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=d82e647a0811181725y3a01f9aanca4cf3ca7e8f3081@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®