From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kbuild@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
hpa@zytor.com
Subject: Re: [PATCH] move some .pci_fixup_* sections into .init
Date: Fri, 8 Apr 2011 12:51:10 -0700 [thread overview]
Message-ID: <20110408125110.52aa90c4@jbarnes-desktop> (raw)
In-Reply-To: <4D5262C30200007800030F9C@vpn.id2.novell.com>
On Wed, 09 Feb 2011 08:47:47 +0000
"Jan Beulich" <JBeulich@novell.com> wrote:
> .pci_fixup_final is only used from .init.text, and hence can (along
> with the respective handler functions) reside in .init.*.
>
> Several other .pci_fixup_* sections are needed only during boot and
> suspend/resume, and can therefore be moved into .init.* if
> !CONFIG_PM_OPS.
>
> While generally section mismatch checking is being turned on by this
> patch for all of .pci_fixup_*, for .pci_fixup_header it is being
> suppressed for the moment as it caused way too much fallout.
> Theoretically, all respective handlers must get their __init/__devinit
> removed, as this gets processed from a non-__init, non-__devinit
> function.
>
> This also adds a previously missing comma in the definition of
> ALL_INIT_DATA_SECTIONS.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@elte.hu>
This didn't apply for me, but I'd be happy to take the PCI parts, can
you re-send against my linux-next branch (assuming it's not already
applied to some other tree).
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-08 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 8:47 [PATCH] move some .pci_fixup_* sections into .init Jan Beulich
2011-04-08 19:51 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-28 8:51 Jan Beulich
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=20110408125110.52aa90c4@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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