From: Jiri Slaby <jirislaby@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
x86@kernel.org, Aristeu Sergio <arozansk@redhat.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH 1/1] X86: pci, fix section mismatch
Date: Mon, 08 Feb 2010 20:15:43 +0100 [thread overview]
Message-ID: <4B7062DF.2020005@gmail.com> (raw)
In-Reply-To: <20100208104426.50bef125@jbarnes-piketon>
On 02/08/2010 07:44 PM, Jesse Barnes wrote:
> On Fri, 29 Jan 2010 10:22:36 +0100
> Jiri Slaby <jslaby@suse.cz> wrote:
>
>> pcibios_scan_specific_bus calls pci_scan_bus_on_node which is
>> __devinit. Mark pcibios_scan_specific_bus __devinit as well since
>> all users are now __init or __devinit.
>>
>> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
>> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
>> Cc: linux-pci@vger.kernel.org
>> Cc: x86@kernel.org
>> ---
>> arch/x86/pci/legacy.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/x86/pci/legacy.c b/arch/x86/pci/legacy.c
>> index a8194c8..8cf7835 100644
>> --- a/arch/x86/pci/legacy.c
>> +++ b/arch/x86/pci/legacy.c
>> @@ -39,7 +39,7 @@ static int __init pci_legacy_init(void)
>> return 0;
>> }
>>
>> -void pcibios_scan_specific_bus(int busn)
>> +void __devinit pcibios_scan_specific_bus(int busn)
>> {
>> int devfn;
>> long node;
>
> Does this apply to some x86 tree that I can't see? Neither my tree nor
> the -tip tree has this function and I don't see it in the history.
Ah, this seems to come from
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/i7core.git#linux_next
as SHA:
a120a84ebbc4cbc9c1addddd2b491e3683b842a6
I'll resend to Mauro.
next prev parent reply other threads:[~2010-02-08 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 9:22 [PATCH 1/1] X86: pci, fix section mismatch Jiri Slaby
2010-02-08 18:44 ` Jesse Barnes
2010-02-08 19:15 ` Jiri Slaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-10 19:42 Jiri Slaby
2010-06-15 13:43 Jiri Slaby
2010-06-18 16:43 ` Jesse Barnes
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=4B7062DF.2020005@gmail.com \
--to=jirislaby@gmail.com \
--cc=arozansk@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=x86@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