public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/4] Add VMID support to nvme-fc transport and lpfc driver
Date: Mon, 16 May 2022 21:40:29 -0400	[thread overview]
Message-ID: <yq15ym5rl7b.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220510200028.37399-1-jsmart2021@gmail.com> (James Smart's message of "Tue, 10 May 2022 13:00:24 -0700")


James,

> This patch adds vmid support to the nvme-fc transport.

Applied to 5.19/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering


      parent reply	other threads:[~2022-05-17  1:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 20:00 [PATCH 0/4] Add VMID support to nvme-fc transport and lpfc driver James Smart
2022-05-10 20:00 ` [PATCH 1/4] nvme-fc: Add new routine nvme_fc_io_getuuid James Smart
2022-05-12  9:50   ` Hannes Reinecke
2022-05-12 23:38   ` Himanshu Madhani
2022-05-16  5:57   ` Christoph Hellwig
2022-05-10 20:00 ` [PATCH 2/4] lpfc: commonize VMID code location James Smart
2022-05-12  9:50   ` Hannes Reinecke
2022-05-12 23:45   ` Himanshu Madhani
2022-05-10 20:00 ` [PATCH 3/4] lpfc: rework lpfc_vmid_get_appid() to be protocol independent James Smart
2022-05-12  9:51   ` Hannes Reinecke
2022-05-12 23:48   ` Himanshu Madhani
2022-05-10 20:00 ` [PATCH 4/4] lpfc: Add support for vmid tagging of NVMe I/Os James Smart
2022-05-12  9:51   ` Hannes Reinecke
2022-05-12 23:50   ` Himanshu Madhani
2022-05-17  1:40 ` 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=yq15ym5rl7b.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=jsmart2021@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.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