public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "René Bolldorf" <xsecute@googlemail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CORRECTED] section mismatch: pcibios_scan_specific_bus()
Date: Sat, 16 Jan 2010 16:13:11 +0100	[thread overview]
Message-ID: <4B51D787.9040409@googlemail.com> (raw)
In-Reply-To: <20100115154020.6823ea3e@jbarnes-piketon>

On 01/16/10 00:40, Jesse Barnes wrote:
> On Wed, 13 Jan 2010 22:41:52 +0100
> René Bolldorf<xsecute@googlemail.com>  wrote:
>
>> Hi all,
>> pcibios_scan_specific_bus() is only invoked from
>> __devinit pcibios_fixup_peer_bridges(void).
>>
>> Mark it as __devinit.
>> Sry for the first mail, I hadn't sleep enough...
>>
>> diff --git a/arch/x86/pci/legacy.c b/arch/x86/pci/legacy.c
>> --- 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;
>
> Doesn't apply to my for-linus branch, also missing a Signed-off-by.  I
> guess you need more sleep. :)  Care to refresh if it's still necessary?
>
> Thanks,

I pulled today 
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 
linux-next. pci legacy was deleted.
Now patch can be ignored.

      reply	other threads:[~2010-01-16 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 21:41 [PATCH][CORRECTED] section mismatch: pcibios_scan_specific_bus() René Bolldorf
2010-01-15 23:40 ` Jesse Barnes
2010-01-16 15:13   ` René Bolldorf [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=4B51D787.9040409@googlemail.com \
    --to=xsecute@googlemail.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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