public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org, ohering@suse.com,
	jbottomley@parallels.com, hch@infradead.org,
	linux-scsi@vger.kernel.org, apw@canonical.com,
	vkuznets@redhat.com, jasowang@redhat.com,
	martin.petersen@oracle.com, hare@suse.de
Subject: Re: [PATCH V4 0/4] scsi: storvsc: Properly support FC hosts
Date: Wed, 06 Jan 2016 16:10:59 -0500	[thread overview]
Message-ID: <yq1lh82ifbw.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1450905327-9497-1-git-send-email-kys@microsoft.com> (K. Y. Srinivasan's message of "Wed, 23 Dec 2015 13:15:27 -0800")

>>>>> "KYS" == K Y Srinivasan <kys@microsoft.com> writes:

The template discussion appears to have lost momentum and since the
concerns were minor I have applied your latest series to 4.5/scsi-queue.

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2016-01-06 21:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 21:15 [PATCH V4 0/4] scsi: storvsc: Properly support FC hosts K. Y. Srinivasan
2015-12-23 21:15 ` [PATCH V4 1/4] scsi: storvsc: Fix a bug in the layout of the hv_fc_wwn_packet K. Y. Srinivasan
2015-12-23 21:15   ` [PATCH V4 2/4] scsi: storvsc: Properly support Fibre Channel devices K. Y. Srinivasan
2015-12-28 12:01     ` Hannes Reinecke
2015-12-28 17:59       ` KY Srinivasan
2015-12-23 21:15   ` [PATCH V4 3/4] scsi: storvsc: Refactor the code in storvsc_channel_init() K. Y. Srinivasan
2015-12-23 21:15   ` [PATCH V4 4/4] scsi: storvsc: Tighten up the interrupt path K. Y. Srinivasan
2016-01-06 21:10 ` 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=yq1lh82ifbw.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=jbottomley@parallels.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ohering@suse.com \
    --cc=vkuznets@redhat.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