From: Adam Belay <abelay@novell.com>
To: Greg KH <greg@kroah.com>, Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] split PCI probing code [1/9]
Date: Thu, 14 Jul 2005 15:54:25 -0400 [thread overview]
Message-ID: <1121370865.3398.108.camel@localhost.localdomain> (raw)
In-Reply-To: <20050714193049.GA31595@kroah.com>
On Thu, 2005-07-14 at 12:30 -0700, Greg KH wrote:
> On Thu, Jul 14, 2005 at 07:10:14PM +0200, Francois Romieu wrote:
> > Adam Belay <abelay@novell.com> :
> > [...]
> >
> > Some nits + a suspect error branch. It seems nice otherwise.
>
> If I'm correct, this patch only moves the code into different files, it
> doesn't change any of it, so your comments apply to the current code
> today, not Adam's changes :)
Correct. I've been trying to make my changes incremental. Nonetheless,
I do appreciate the comments. I'll try to apply these fixes to my
current tree.
Thanks,
Adam
next prev parent reply other threads:[~2005-07-14 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 8:55 [RFC][PATCH] split PCI probing code [1/9] Adam Belay
2005-07-14 17:10 ` Francois Romieu
2005-07-14 19:30 ` Greg KH
2005-07-14 19:54 ` Adam Belay [this message]
2005-07-14 20:00 ` Francois Romieu
2005-07-14 19:14 ` John Rose
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=1121370865.3398.108.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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