From: "hch@lst.de" <hch@lst.de>
To: Saurav Kashyap <skashyap@marvell.com>
Cc: "hch@lst.de" <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Nilesh Javali <njavali@marvell.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
GR-QLogic-Storage-Upstream
<GR-QLogic-Storage-Upstream@marvell.com>,
"james.smart@broadcom.com" <james.smart@broadcom.com>,
"axboe@fb.com" <axboe@fb.com>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [EXT] Re: [PATCH 0/2] qla2xxx - add nvme map_queues support
Date: Wed, 13 Oct 2021 07:11:15 +0200 [thread overview]
Message-ID: <20211013051115.GA25113@lst.de> (raw)
In-Reply-To: <DM6PR18MB30342CF2C3CB23EE3B947841D2B79@DM6PR18MB3034.namprd18.prod.outlook.com>
On Wed, Oct 13, 2021 at 05:09:04AM +0000, Saurav Kashyap wrote:
> Hi Christoph,
>
> > > Hi Sagi/Christoph,
> > >
> > > I haven't heard anything on this and there are no review comments on this
> > patch set, kindly include this in nvme tree.
> > >
> >
> > I'll queue this up once the 5.16 tree opens unless James voices any
> > objections.
>
> Any updates on this one?
http://git.infradead.org/nvme.git/commitdiff/062b5291ef352d6198c6c8414c71ae2debd06cf7
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Saurav Kashyap <skashyap@marvell.com>
Cc: "hch@lst.de" <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Nilesh Javali <njavali@marvell.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
GR-QLogic-Storage-Upstream
<GR-QLogic-Storage-Upstream@marvell.com>,
"james.smart@broadcom.com" <james.smart@broadcom.com>,
"axboe@fb.com" <axboe@fb.com>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [EXT] Re: [PATCH 0/2] qla2xxx - add nvme map_queues support
Date: Wed, 13 Oct 2021 07:11:15 +0200 [thread overview]
Message-ID: <20211013051115.GA25113@lst.de> (raw)
In-Reply-To: <DM6PR18MB30342CF2C3CB23EE3B947841D2B79@DM6PR18MB3034.namprd18.prod.outlook.com>
On Wed, Oct 13, 2021 at 05:09:04AM +0000, Saurav Kashyap wrote:
> Hi Christoph,
>
> > > Hi Sagi/Christoph,
> > >
> > > I haven't heard anything on this and there are no review comments on this
> > patch set, kindly include this in nvme tree.
> > >
> >
> > I'll queue this up once the 5.16 tree opens unless James voices any
> > objections.
>
> Any updates on this one?
http://git.infradead.org/nvme.git/commitdiff/062b5291ef352d6198c6c8414c71ae2debd06cf7
next prev parent reply other threads:[~2021-10-13 5:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 12:56 [PATCH 0/2] qla2xxx - add nvme map_queues support Nilesh Javali
2021-08-23 12:56 ` Nilesh Javali
2021-08-23 12:56 ` [PATCH 1/2] nvme-fc: Add support for map_queues Nilesh Javali
2021-08-23 12:56 ` Nilesh Javali
2021-08-23 12:56 ` [PATCH 2/2] qla2xxx: Add map_queues support to nvme Nilesh Javali
2021-08-23 12:56 ` Nilesh Javali
2021-08-23 17:21 ` [PATCH 0/2] qla2xxx - add nvme map_queues support Sagi Grimberg
2021-08-23 17:21 ` Sagi Grimberg
2021-08-24 3:38 ` Saurav Kashyap
2021-08-24 3:38 ` Saurav Kashyap
2021-08-24 3:46 ` Ming Lei
2021-08-24 3:46 ` Ming Lei
2021-08-25 4:58 ` [EXT] " Saurav Kashyap
2021-08-25 4:58 ` Saurav Kashyap
2021-09-07 9:18 ` Saurav Kashyap
2021-09-07 9:18 ` Saurav Kashyap
2021-09-14 8:07 ` Saurav Kashyap
2021-09-14 8:07 ` Saurav Kashyap
2021-09-14 8:32 ` hch
2021-09-14 8:32 ` hch
2021-09-22 4:28 ` Saurav Kashyap
2021-09-22 4:28 ` Saurav Kashyap
2021-10-13 5:09 ` Saurav Kashyap
2021-10-13 5:09 ` Saurav Kashyap
2021-10-13 5:11 ` hch [this message]
2021-10-13 5:11 ` hch
2021-09-14 9:31 ` Daniel Wagner
2021-09-14 9:31 ` Daniel Wagner
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=20211013051115.GA25113@lst.de \
--to=hch@lst.de \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=axboe@fb.com \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=njavali@marvell.com \
--cc=sagi@grimberg.me \
--cc=skashyap@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.