From: Christoph Hellwig <hch@lst.de>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: yaminf@mellanox.com, Sagi Grimberg <sagi@grimberg.me>,
idanb@mellanox.com, israelr@mellanox.com,
linux-nvme@lists.infradead.org, shlomin@mellanox.com,
Jason Gunthorpe <jgg@nvidia.com>,
kbusch@kernel.org, ogerlitz@mellanox.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/3] nvme-rdma: assign completion vector correctly
Date: Wed, 24 Jun 2020 10:46:33 +0200 [thread overview]
Message-ID: <20200624084633.GA24240@lst.de> (raw)
In-Reply-To: <0e102b77-79bb-0dc6-48e7-10cc3aefc9a8@mellanox.com>
On Wed, Jun 24, 2020 at 11:44:06AM +0300, Max Gurtovoy wrote:
>> I don't think 1+2 are 5.8 material, so please just resend 3 standalone
>> for now, and then resend 1+2 once I've merged it and rebased nvme-5.9
>> on top of nvme-5.8.
>
> Ok. Actually 1+2 were aimed to be merged to 5.8 but created a conflict
> between Jason's and Jens's trees.
>
> If we go this way it means we can't push new features to RDMA and use it in
> NVMf in the same cycle.
>
> Jason,
>
> can we push iSER CQ sharing to kernel-5.8 ?
We're not going to merge new features in nvme after -rc2. For cross
subsystem coordination either everything needs to go in through one
tree if possible, or we'll need shared branches.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-06-24 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 14:55 [PATCH 0/3] NVMe/RDMA patches for 5.8 Max Gurtovoy
2020-06-23 14:55 ` [PATCH 1/3] nvme-rdma: use new shared CQ mechanism Max Gurtovoy
2020-06-23 14:55 ` [PATCH 2/3] nvmet-rdma: " Max Gurtovoy
2020-06-23 14:55 ` [PATCH 3/3] nvme-rdma: assign completion vector correctly Max Gurtovoy
2020-06-23 15:22 ` Jason Gunthorpe
2020-06-23 17:34 ` Sagi Grimberg
2020-06-24 8:34 ` Max Gurtovoy
2020-06-24 8:37 ` Christoph Hellwig
2020-06-24 8:44 ` Max Gurtovoy
2020-06-24 8:46 ` Christoph Hellwig [this message]
2020-06-24 14:22 ` Jason Gunthorpe
2020-06-24 15:14 ` Max Gurtovoy
2020-06-24 16:41 ` Christoph Hellwig
2020-06-25 8:11 ` Max Gurtovoy
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=20200624084633.GA24240@lst.de \
--to=hch@lst.de \
--cc=idanb@mellanox.com \
--cc=israelr@mellanox.com \
--cc=jgg@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=sagi@grimberg.me \
--cc=shlomin@mellanox.com \
--cc=yaminf@mellanox.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.