From: Greg KH <gregkh@suse.de>
To: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [RFC/PATCH] unregister_node() for hotplug use
Date: Mon, 25 Apr 2005 23:54:32 -0700 [thread overview]
Message-ID: <20050426065431.GB5889@suse.de> (raw)
In-Reply-To: <20050425230333.6b8dfb33.tokunaga.keiich@jp.fujitsu.com>
On Mon, Apr 25, 2005 at 11:03:33PM +0900, Keiichiro Tokunaga wrote:
> On Fri, 22 Apr 2005 11:32:11 +0900 Keiichiro Tokunaga wrote:
> > On Thu, 21 Apr 2005 17:39:20 -0700 Greg KH wrote:
> > > On Fri, Apr 22, 2005 at 12:30:09AM +0900, Keiichiro Tokunaga wrote:
> > > > +#ifdef CONFIG_HOTPLUG
> > > > +void unregister_node(struct node *node)
> > > > +{
> > > > + sysdev_remove_file(&node->sysdev, &attr_cpumap);
> > > > + sysdev_remove_file(&node->sysdev, &attr_meminfo);
> > > > + sysdev_remove_file(&node->sysdev, &attr_numastat);
> > > > + sysdev_remove_file(&node->sysdev, &attr_distance);
> > > > +
> > > > + sysdev_unregister(&node->sysdev);
> > > > +}
> > > > +EXPORT_SYMBOL_GPL(register_node);
> > > > +EXPORT_SYMBOL_GPL(unregister_node);
> > > > +#else /* !CONFIG_HOTPLUG */
> > > > +void unregister_node(struct node *node)
> > > > +{
> > > > +}
> > > > +#endif /* !CONFIG_HOTPLUG */
> <snip>
> > > And hey, what's the real big deal here, why not always have this
> > > function no matter if CONFIG_HOTPLUG is enabled or not? I really want
> > > to just make that an option that is always enabled anyway, but changable
> > > if you are using CONFIG_TINY or something...
> >
> > I put the #ifdef there for users who don't need hotplug
> > stuffs, but I want to make the option always enabled, too.
> > Also a good side effect, the code would be cleaner:) I
> > will be updating my patch without the #ifdef and sending
> > it here.
>
> Here is the patch. Please apply.
Care to resend it with a proper change log description that I can use?
thanks,
greg k-h
next prev parent reply other threads:[~2005-04-26 6:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 12:07 [RFC/PATCH] unregister_node() for hotplug use Keiichiro Tokunaga
2005-04-20 12:35 ` Arjan van de Ven
2005-04-21 9:25 ` Keiichiro Tokunaga
2005-04-20 17:32 ` Greg KH
2005-04-21 15:30 ` Keiichiro Tokunaga
2005-04-22 0:39 ` Greg KH
2005-04-22 2:32 ` Keiichiro Tokunaga
2005-04-25 14:03 ` Keiichiro Tokunaga
2005-04-26 6:54 ` Greg KH [this message]
2005-04-28 0:17 ` Keiichiro Tokunaga
2005-05-07 12:11 ` Keiichiro Tokunaga
2005-05-08 0:26 ` Nathan Lynch
2005-05-08 12:28 ` Keiichiro Tokunaga
2005-05-09 22:44 ` Matthew Dobson
2005-05-10 11:20 ` Keiichiro Tokunaga
2005-05-10 18:15 ` Matthew Dobson
2005-05-10 18:45 ` Greg KH
2005-05-10 18:58 ` Matthew Dobson
2005-05-10 20:11 ` Greg KH
2005-05-10 20:13 ` Matthew Dobson
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=20050426065431.GB5889@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tokunaga.keiich@jp.fujitsu.com \
/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.