[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120111104940.GA5394@infradead.org>
Date: Wed, 11 Jan 2012 05:49:40 -0500
From: Christoph Hellwig <hch@...radead.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
Bart Van Assche <bvanassche@....org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
target-devel <target-devel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Roland Dreier <roland@...nel.org>,
J?rn Engel <joern@...estorage.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [GIT PULL] target: Updates for v3.3-rc1 (round 1)
On Tue, Jan 10, 2012 at 01:51:07PM -0600, James Bottomley wrote:
> > The changes since the Nov 4 RFC are listed in the patch commit log:
> >
> > ib_srpt: Make compilation with BUG=n proceed`
> > ib_srpt: Use new target_core_fabric.h include
> > ib_srpt: Check hex2bin() return code to silence build warning
> >
> > These are all very minor and did not warrant another full RFC posting.
>
> They might not warrant a full RFC reposting, but individually they
> should have been posted to the list, so Bart is right.
At least 2 and 3 list, just not as global patches against the
target tree, not ib_srpt specificly:
2 is from: [PATCH] target: header reshuffle, part2
3 is from: [PATCH 5/5] target: check hex2bin result
Not sure about 1.
I'm really getting tired of this bickering. It's a brand new driver and
doesn't have to be perfect. While Bart generally has technically good
points there's really no reason to put his remaining fixups in after
the driver has been merged and available to a wieder audience.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists