From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Steffen Maier <maier@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH RESEND 0/9] zfcp features and bugfixes for 3.10 merge window
Date: Fri, 26 Apr 2013 09:10:44 -0700 [thread overview]
Message-ID: <1366992644.14612.1.camel@dabdike> (raw)
In-Reply-To: <517AA0E9.6060008@linux.vnet.ibm.com>
On Fri, 2013-04-26 at 17:44 +0200, Steffen Maier wrote:
> On 04/26/2013 05:10 PM, James Bottomley wrote:
> > On Fri, 2013-04-26 at 16:13 +0200, Steffen Maier wrote:
> >> James,
> >>
> >> here is a series of zfcp features and bugfixes.
> >> We would very much appreciate if you could integrate them for the
> >> upcoming merge window preparing kernel v3.10.
> >> The patches apply on top of the current misc branch of your scsi.git.
> >>
> >> Apparently, I did something wrong on git-send-email so the mails
> >> did not appear on the mailing lists. Apologies for resending.
> >
> > Since no-one saw the originals, apologies aren't necessary.
> > Unfortunately, you're still missing three patches: 5,6,9/9
>
> Hm, just the patches that had something like this in the signature area:
> Cc: <stable@vger.kernel.org> #2.6.37+
> I guess they got stuck because some MTA or the list do not like what
> git-send-email converted this into as a CC recipient:
> <stable@vger.kernel.org> #2.6.37+
Hm, that would appear to be a bug in git-send-email. You can turn off
these with the --suppress-cc=cc flag I think.
> I resent those three as replies to the stuck/lost ones.
Got them now, thanks
James
next prev parent reply other threads:[~2013-04-26 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:13 [PATCH RESEND 0/9] zfcp features and bugfixes for 3.10 merge window Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 1/9] zfcp: cfdc fops add owner Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 2/9] zfcp: cleanup port sysfs attribute usage Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 3/9] zfcp: cleanup unit " Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 4/9] zfcp: remove unused device_unregister wrapper Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 7/9] zfcp: module parameter dbflevel for early debugging Steffen Maier
2013-04-26 14:13 ` [PATCH RESEND 8/9] zfcp: remove access control tables interface Steffen Maier
2013-04-26 15:10 ` [PATCH RESEND 0/9] zfcp features and bugfixes for 3.10 merge window James Bottomley
2013-04-26 15:44 ` Steffen Maier
2013-04-26 16:10 ` James Bottomley [this message]
2013-04-27 9:44 ` Heiko Carstens
[not found] ` <1366985635-38270-6-git-send-email-maier@linux.vnet.ibm.com>
2013-04-26 15:32 ` [PATCH RESEND 5/9] zfcp: fix adapter (re)open recovery while link to SAN is down Steffen Maier
[not found] ` <1366985635-38270-7-git-send-email-maier@linux.vnet.ibm.com>
2013-04-26 15:33 ` [PATCH RESEND 6/9] zfcp: block queue limits with data router Steffen Maier
[not found] ` <1366985635-38270-10-git-send-email-maier@linux.vnet.ibm.com>
2013-04-26 15:34 ` [PATCH RESEND 9/9] zfcp: status read buffers on first adapter open with link down Steffen Maier
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=1366992644.14612.1.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.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