From: jbarnes@sgi.com (Jesse Barnes)
To: Christoph Hellwig <hch@infradead.org>, Pat Gefre <pfg@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updating our sn code in 2.6
Date: Mon, 29 Dec 2003 15:41:40 -0800 [thread overview]
Message-ID: <20031229234140.GA29575@sgi.com> (raw)
In-Reply-To: <20031228143603.A20391@infradead.org>
On Sun, Dec 28, 2003 at 02:36:03PM +0000, Christoph Hellwig wrote:
> - no change in 000-hwgfs-update.patch.inprogress, hwgraph_path_lookup
> shall not be reintroduced.
Pat, it looks like hwgraph_path_lookup() is only used in the PCI hotplug
code, and is messed up anyway (it's looking for a SCSI controller??), so
we can probably kill the addition of that function.
> - 014-cleanup-pci.c.patch: no change apparently?
Yeah, it would be nice to avoid introducing stuff that just gets deleted
in later patches.
> - 030-pciio-cleanup.patch: Dito
Not sure what this is about...
> - 071-xswitch.devfunc.patch: Dito.
Yes, I think we do have more xswitches coming...
> - 075-rename-reorg.patch: Dito
If this stuff is going to be used by more than just ia64, it should
probably be moved to another directory/file.
> > David or Andrew can you take these patches ?
>
> Really, that's not what I consider fixing. Please fix up
> 000,014 and 030 and drop 071 and 075, then it should be fine for
> merging. 071 shouldn't go in at all and 075 needs the renaming killed,
> everything else can go in although it's not nice.
Pat, will the patches work if we omit 071 and 075? If so, maybe we can
get the others merged in and continue to work on the last two.
Jesse
next prev parent reply other threads:[~2003-12-29 23:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 2:59 [PATCH] Updating our sn code in 2.6 Pat Gefre
2003-12-19 11:43 ` Christoph Hellwig
2003-12-20 0:35 ` Pat Gefre
2003-12-20 1:24 ` Jesse Barnes
2003-12-20 3:05 ` Jesse Barnes
2003-12-20 12:27 ` Christoph Hellwig
2003-12-23 2:55 ` Pat Gefre
2003-12-23 9:02 ` Christoph Hellwig
2003-12-23 14:46 ` Colin Ngam
2003-12-23 16:55 ` Christoph Hellwig
2003-12-26 19:42 ` Colin Ngam
2003-12-28 14:44 ` Christoph Hellwig
2003-12-28 16:32 ` Colin Ngam
2003-12-28 17:22 ` Christoph Hellwig
2003-12-29 1:10 ` Colin Ngam
2003-12-29 1:21 ` Colin Ngam
2003-12-28 14:36 ` Christoph Hellwig
2003-12-29 23:41 ` Jesse Barnes [this message]
2003-12-30 21:21 ` Pat Gefre
2003-12-30 21:24 ` Christoph Hellwig
2004-01-02 19:47 ` Patrick Gefre
2004-01-02 20:11 ` Christoph Hellwig
2004-03-29 15:39 ` Christoph Hellwig
2004-03-29 15:39 ` Patrick Gefre
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 23:31 Pat Gefre
2003-11-07 10:25 ` Christoph Hellwig
2003-11-13 0:26 ` Pat Gefre
2003-11-13 2:42 ` Paul Jackson
2003-11-13 6:58 ` Christoph Hellwig
2003-11-13 16:48 ` Jesse Barnes
2003-11-14 12:10 ` Christoph Hellwig
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=20031229234140.GA29575@sgi.com \
--to=jbarnes@sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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