From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Benjamin Block <bblock@linux.ibm.com>
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Steffen Maier <maier@linux.ibm.com>,
Fedor Loshakov <loshakov@linux.ibm.com>,
Jens Remus <jremus@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 0/3] zfcp: fixes for the zFCP device driver
Date: Thu, 11 Jul 2019 21:06:08 -0400 [thread overview]
Message-ID: <yq1pnmg6ozj.fsf@oracle.com> (raw)
In-Reply-To: <cover.1562098940.git.bblock@linux.ibm.com> (Benjamin Block's message of "Tue, 2 Jul 2019 23:01:59 +0200")
Benjamin,
> So please consider them for the next cycle. Or should I not have send
> them in that case? Sorry, this step of the process was a bit unclear
> to me.
A fix is a fix. Applied the series to 5.3/scsi-fixes. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-07-12 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 21:01 [PATCH 0/3] zfcp: fixes for the zFCP device driver Benjamin Block
2019-07-02 21:02 ` [PATCH 1/3] zfcp: fix request object use-after-free in send path causing seqno errors Benjamin Block
2019-07-02 21:02 ` [PATCH 2/3] zfcp: fix request object use-after-free in send path causing wrong traces Benjamin Block
2019-07-02 21:02 ` [PATCH 3/3] zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized Benjamin Block
2019-07-12 1:06 ` Martin K. Petersen [this message]
2019-07-12 13:16 ` [PATCH 0/3] zfcp: fixes for the zFCP device driver Benjamin Block
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=yq1pnmg6ozj.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bblock@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=jremus@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loshakov@linux.ibm.com \
--cc=maier@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.