From: Andrew Morton <akpm@osdl.org>
To: Jake Moilanen <moilanen@austin.ibm.com>
Cc: torvalds@osdl.org, greg@kroah.com, linux-kernel@vger.kernel.org,
linuxppc64-dev@lists.linuxppc.org
Subject: Re: Fw: [PATCH][2.6] PCI Scan all functions
Date: Thu, 29 Jan 2004 15:30:15 -0800 [thread overview]
Message-ID: <20040129153015.0e77f8e7.akpm@osdl.org> (raw)
In-Reply-To: <1075417841.679.139.camel@magik>
Jake Moilanen <moilanen@austin.ibm.com> wrote:
>
> On Tue, 2004-01-27 at 18:09, Linus Torvalds wrote:
> > On Tue, 27 Jan 2004, Jake Moilanen wrote:
> > >
> > > I tried this patch on my one (and only) machine that exibits this
> > > issue. Everything was detected correctly.
> >
> > Ok. This at least looks more palatable in that it's now confined a bit
> > better.
> >
> > However, looking at the logic, we really only want to do the
> > "pcibios_scan_all_fns()" once per device, not once for each function, no?
> >
> > Linus
>
> Here's a patch that addresses Linus's concerns. Andrew, if you have no
> objections, please apply.
Could you please send me a changelog description for this patch? A bit of
background for posterity, so other kernel developers can come in a year
hence and answer the question "what's all this about then?". Thanks.
next prev parent reply other threads:[~2004-01-29 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040127130803.10b666f3.akpm@osdl.org>
[not found] ` <Pine.LNX.4.58.0401271345060.10794@home.osdl.org>
[not found] ` <1075241556.681.19.camel@magik>
[not found] ` <Pine.LNX.4.58.0401271428340.10794@home.osdl.org>
[not found] ` <1075247559.672.33.camel@magik>
[not found] ` <Pine.LNX.4.58.0401271559230.10794@home.osdl.org>
2004-01-29 23:10 ` Fw: [PATCH][2.6] PCI Scan all functions Jake Moilanen
2004-01-29 23:30 ` Andrew Morton [this message]
2004-01-30 14:10 ` Jake Moilanen
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=20040129153015.0e77f8e7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=moilanen@austin.ibm.com \
--cc=torvalds@osdl.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 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.