From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Daniel Wagner <dwagner@suse.de>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Hannes Reinecke <hare@suse.de>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH v6 0/6] nvme: add csi, ms and nuse to sysfs
Date: Tue, 19 Dec 2023 18:26:42 +0200 [thread overview]
Message-ID: <6f56726b-8deb-4e67-bdeb-4cfbe56237b0@nvidia.com> (raw)
In-Reply-To: <ZYG_zlnvfLOJHEJM@kbusch-mbp>
On 19/12/2023 18:07, Keith Busch wrote:
> On Tue, Dec 19, 2023 at 04:42:20PM +0200, Max Gurtovoy wrote:
>> Hi Keith,
>>
>> On 19/12/2023 0:55, Keith Busch wrote:
>>> On Mon, Dec 18, 2023 at 05:59:48PM +0100, Daniel Wagner wrote:
>>>> Rebased on the current nvme/nvme-6.8 branch and added the Review tags. Also
>>>> addressed the printk format issue pointed out by Chaitanya.
>>>
>>> Thanks, added to nvme-6.8.
>>
>> I'm rebasing my fixes to the PI bug (which are not trivial) on top of
>> nvme-6.8 and Daniel's series.
>> I've found that this branch is missing some fixes from the master that I've
>> added manually to local nvme-6.8 branch.
>> When do you plan to rebase the nvme-6.8 on top of master ?
>> It will be helpful, otherwise my patches will not apply cleanly on your
>> branch. :)
>
> linux-nvme pulls go through Jens' linux-block repo, so we have to be
> based on the appropriate branch from there. We already have some late
> fixes in 6.7 that create minor merge conflicts for our existing 6.8
> branch, so we may provide a reference resolution branch with the pull
> request if conflicts are non-trivial. That might be an option for your
> fixes if you can make them work atop existing nvme-6.8 without the
> conflicting 6.7 changes.
>
> Sometime after the next merge window opens, Jens will rebase his 6.8
> block tree to Linus', and we usually get a 2nd feature pull request
> within the merge window from that new baseline. That might be an option
> if you want to wait a couple more weeks.
I see. I think that after finishing the latest testing I'll send the
version on top of nvme-6.8 + my local branch patches I took from 6.7.
We will start the reviewing process and probably will converge in a week
or two. Then we will see what is the status of the linux-block repo and
decide how to continue.
prev parent reply other threads:[~2023-12-19 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 16:59 [PATCH v6 0/6] nvme: add csi, ms and nuse to sysfs Daniel Wagner
2023-12-18 16:59 ` [PATCH v6 1/6] nvme: move ns id info to struct nvme_ns_head Daniel Wagner
2023-12-19 11:56 ` Hannes Reinecke
2023-12-19 12:54 ` Sagi Grimberg
2023-12-18 16:59 ` [PATCH v6 2/6] nvme: refactor ns info helpers Daniel Wagner
2023-12-19 11:57 ` Hannes Reinecke
2023-12-18 16:59 ` [PATCH v6 3/6] nvme: refactor ns info setup function Daniel Wagner
2023-12-19 11:57 ` Hannes Reinecke
2023-12-18 16:59 ` [PATCH v6 4/6] nvme: rename ns attribute group Daniel Wagner
2023-12-19 11:58 ` Hannes Reinecke
2023-12-18 16:59 ` [PATCH v6 5/6] nvme: add csi, ms and nuse to sysfs Daniel Wagner
2023-12-19 11:58 ` Hannes Reinecke
2023-12-18 16:59 ` [PATCH v6 6/6] nvme: repack struct nvme_ns_head Daniel Wagner
2023-12-19 11:59 ` Hannes Reinecke
2023-12-18 22:55 ` [PATCH v6 0/6] nvme: add csi, ms and nuse to sysfs Keith Busch
2023-12-19 14:42 ` Max Gurtovoy
2023-12-19 16:07 ` Keith Busch
2023-12-19 16:26 ` Max Gurtovoy [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=6f56726b-8deb-4e67-bdeb-4cfbe56237b0@nvidia.com \
--to=mgurtovoy@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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