From: Greg KH <greg@kroah.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arch@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>,
Adrian Bunk <bunk@kernel.org>
Subject: Re: [PATCH] Use separate sections for __dev/__cpu/__mem code/data
Date: Tue, 22 Jan 2008 13:17:15 -0800 [thread overview]
Message-ID: <20080122211715.GA26279@kroah.com> (raw)
In-Reply-To: <1200859743-24037-8-git-send-email-sam@ravnborg.org>
On Sun, Jan 20, 2008 at 09:09:03PM +0100, Sam Ravnborg wrote:
> Introducing separate sections for __dev* (HOTPLUG),
> __cpu* (HOTPLUG_CPU) and __mem* (MEMORY_HOTPLUG)
> allows us to do a much more reliable Section mismatch
> check in modpost. We are no longer dependent on the actual
> configuration of for example HOTPLUG.
>
> This has the effect that all users see much more
> Section mismatch warnings than before because they
> were almost all hidden when HOTPLUG was enabled.
> The advantage of this is that when building a piece
> of code then it is much more likely that the Section
> mismatch errors are spotted and the warnings will be
> felt less random of nature.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> Cc: Greg KH <greg@kroah.com>
> Cc: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Adrian Bunk <bunk@kernel.org>
I like this a lot. It makes things much more understandable from a
driver developer's point of view, and would allow us to mark some things
as freeable when we do not run with a CPU hotplug system :)
Feel free to add a:
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
to the patch, if you want to take it in your tree.
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-22 21:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 20:05 kbuild: improved Section mismatch detection Sam Ravnborg
2008-01-20 20:08 ` [PATCH] kbuild: fix so modpost can now check any .o file Sam Ravnborg
2008-01-20 20:08 ` [PATCH] kbuild: try harder to find symbol names in modpost Sam Ravnborg
2008-01-20 20:08 ` [PATCH] kbuild: code refactoring " Sam Ravnborg
2008-01-20 20:08 ` [PATCH] kbuild: introduce blacklisting " Sam Ravnborg
2008-01-20 20:09 ` [PATCH] kbuild: check section names consistently " Sam Ravnborg
2008-01-20 20:09 ` [PATCH] all archs: consolidate init and exit sections in vmlinux.lds.h Sam Ravnborg
2008-01-20 20:09 ` [PATCH] compiler.h: introduce __section() Sam Ravnborg
2008-01-20 20:09 ` [PATCH] Use separate sections for __dev/__cpu/__mem code/data Sam Ravnborg
2008-01-21 7:33 ` Paul Mundt
2008-01-21 9:57 ` Sam Ravnborg
2008-01-21 10:29 ` Andreas Schwab
2008-01-21 10:45 ` Sam Ravnborg
2008-01-21 10:47 ` Sam Ravnborg
2008-01-21 10:52 ` Paul Mundt
2008-01-21 12:06 ` Sam Ravnborg
2008-01-22 0:56 ` Paul Mundt
2008-01-22 3:25 ` Sam Ravnborg
2008-01-22 21:17 ` Greg KH [this message]
2008-01-22 21:25 ` Russell King
2008-01-21 1:00 ` [PATCH] kbuild: introduce blacklisting in modpost Rusty Russell
2008-01-21 0:56 ` [PATCH] kbuild: fix so modpost can now check any .o file Rusty Russell
2008-01-21 6:11 ` Sam Ravnborg
2008-01-20 21:33 ` kbuild: improved Section mismatch detection Sam Ravnborg
2008-01-20 22:27 ` Adrian Bunk
2008-01-21 2:51 ` Sam Ravnborg
2008-01-21 20:31 ` Sam Ravnborg
2008-01-21 20:56 ` Adrian Bunk
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=20080122211715.GA26279@kroah.com \
--to=greg@kroah.com \
--cc=bunk@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).