From: Dan Williams <dan.j.williams@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
Jeff Skirvin <jeffrey.d.skirvin@intel.com>,
David Milburn <dmilburn@redhat.com>,
Dave Jiang <dave.jiang@intel.com>,
Ed Ciechanowski <ed.ciechanowski@intel.com>,
Ed Nadolski <edmund.nadolski@intel.com>,
Jacek Danecki <jacek.danecki@intel.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT] isci: fixes and cleanups
Date: Wed, 23 Mar 2011 01:04:55 -0700 [thread overview]
Message-ID: <AANLkTi=UHZ-=LsApBic-fpFRGxeJULFh621bWvjLusCy@mail.gmail.com> (raw)
In-Reply-To: <20110318153829.GA13169@infradead.org>
On Fri, Mar 18, 2011 at 8:38 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Fri, Mar 18, 2011 at 11:18:07AM -0400, Christoph Hellwig wrote:
>> Care to post a patch, or in case it's too large a patch link? git trees
>> are inherently unreviewable.
>
> Sorry, just noticed the patch series. I still don't quite see the
> connection between the series and the tree, but I'll assume they end up
> with the same result.
>
They will end up with the same result. I'm assuming the in-progress
rework state is not that interesting to post every patch to
linux-scsi.
As we have release candidates I will reflow the patch series
(lldd+core) for review.
--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-03-23 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 8:55 [GIT] isci: fixes and cleanups Dan Williams
2011-03-18 15:18 ` Christoph Hellwig
2011-03-18 15:38 ` Christoph Hellwig
2011-03-23 8:04 ` Dan Williams [this message]
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='AANLkTi=UHZ-=LsApBic-fpFRGxeJULFh621bWvjLusCy@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@suse.de \
--cc=dave.jiang@intel.com \
--cc=dmilburn@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=hch@infradead.org \
--cc=jacek.danecki@intel.com \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).