From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Bart Van Assche <bvanassche@acm.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
target-devel <target-devel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Roland Dreier <roland@kernel.org>,
J?rn Engel <joern@purestorage.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [GIT PULL] target: Updates for v3.3-rc1 (round 1)
Date: Wed, 11 Jan 2012 05:49:40 -0500 [thread overview]
Message-ID: <20120111104940.GA5394@infradead.org> (raw)
In-Reply-To: <1326225067.3264.51.camel@dabdike.int.hansenpartnership.com>
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.
next prev parent reply other threads:[~2012-01-11 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 18:56 Nicholas A. Bellinger
2012-01-10 19:19 ` Bart Van Assche
2012-01-10 19:33 ` Nicholas A. Bellinger
2012-01-10 19:51 ` James Bottomley
2012-01-10 21:04 ` Nicholas A. Bellinger
2012-01-11 10:49 ` Christoph Hellwig [this message]
2012-01-14 15:19 ` James Bottomley
2012-01-11 6:57 ` Bart Van Assche
2012-01-11 19:32 ` Nicholas A. Bellinger
2012-01-13 23:02 ` Nicholas A. Bellinger
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=20120111104940.GA5394@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bigeasy@linutronix.de \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=roland@kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome