From: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, nab@linux-iscsi.org,
brking@linux.vnet.ibm.com, imunsie@au1.ibm.com,
dja@ozlabs.au.ibm.com, andrew.donnellan@au1.ibm.com,
mikey@neuling.org, linuxppc-dev@lists.ozlabs.org,
Manoj Kumar <kumarmn@us.ibm.com>,
"Manoj N. Kumar" <manoj@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 01/30] cxlflash: Fix to avoid invalid port_sel value
Date: Wed, 16 Sep 2015 16:09:29 -0500 [thread overview]
Message-ID: <C47C20BA-B972-4193-950C-07A4A547503A@linux.vnet.ibm.com> (raw)
In-Reply-To: <1442431127.2234.28.camel@HansenPartnership.com>
> On Sep 16, 2015, at 2:18 PM, James Bottomley =
<James.Bottomley@HansenPartnership.com> wrote:
>=20
> Could you please add a cover letter (a 0/30) and thread your patches
> from that? For large patch series, it really does make following
> everything a lot easier for me (and most other people who use a =
threaded
> mail reader).
James,
My mistake. I'll send out a properly threaded series shortly.
-matt=
next prev parent reply other threads:[~2015-09-16 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 16:51 [PATCH v2 01/30] cxlflash: Fix to avoid invalid port_sel value Matthew R. Ochs
2015-09-16 19:18 ` James Bottomley
2015-09-16 21:09 ` Matthew R. Ochs [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-16 21:23 [PATCH v2 00/30] cxlflash: Miscellaneous bug fixes and corrections Matthew R. Ochs
2015-09-16 21:25 ` [PATCH v2 01/30] cxlflash: Fix to avoid invalid port_sel value Matthew R. Ochs
2015-09-18 1:16 ` Brian King
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=C47C20BA-B972-4193-950C-07A4A547503A@linux.vnet.ibm.com \
--to=mrochs@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=dja@ozlabs.au.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=kumarmn@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=nab@linux-iscsi.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).