From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Martin Wilck <Martin.Wilck@suse.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Himanshu Madhani <hmadhani@marvell.com>,
Quinn Tran <qutran@marvell.com>,
"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Daniel Wagner" <dwagner@suse.de>,
James Bottomley <jejb@linux.vnet.ibm.com>
Subject: Re: [PATCH RESEND v2] fixup "qla2xxx: Optimize NPIV tear down process"
Date: Wed, 06 Nov 2019 00:01:58 -0500 [thread overview]
Message-ID: <yq136f138e1.fsf@oracle.com> (raw)
In-Reply-To: <20191105145550.10268-1-martin.wilck@suse.com> (Martin Wilck's message of "Tue, 5 Nov 2019 14:56:00 +0000")
Martin,
Applied to 5.4/scsi-fixes, thanks.
Next time, please run checkpatch on your patch and please make sure you
get the ordering of commit description and commentary/changelog right.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-06 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 14:56 [PATCH RESEND v2] fixup "qla2xxx: Optimize NPIV tear down process" Martin Wilck
2019-11-05 15:04 ` Himanshu Madhani
2019-11-06 5:01 ` Martin K. Petersen [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=yq136f138e1.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Martin.Wilck@suse.com \
--cc=dwagner@suse.de \
--cc=hmadhani@marvell.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=qutran@marvell.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.