From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fix for Linux 6.12
Date: Thu, 14 Nov 2024 11:28:15 -0700 [thread overview]
Message-ID: <058d94f1-da1d-49d4-aeb9-10fda3069c99@kernel.dk> (raw)
In-Reply-To: <ZzY_Q785-p12Bl14@kbusch-mbp>
On 11/14/24 11:19 AM, Keith Busch wrote:
> Same fix as the last week's nvme fix, but for nvme-multipath. It should
> have been included with our previous pull-request, but I did see the
> message in my queue until too late.
Just to avoid yet another merge conflict, can we please just push this
to 6.13 instead and just mark it stable? We probably should've done that
with the other one as well, it's not like they are important fixes.
--
Jens Axboe
next prev parent reply other threads:[~2024-11-14 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 18:19 [GIT PULL] nvme fix for Linux 6.12 Keith Busch
2024-11-14 18:28 ` Jens Axboe [this message]
2024-11-14 18:41 ` Keith Busch
2024-11-14 18:45 ` Jens Axboe
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=058d94f1-da1d-49d4-aeb9-10fda3069c99@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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