From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme updates for Linux 6.15
Date: Thu, 20 Mar 2025 18:40:00 -0600 [thread overview]
Message-ID: <5d0f0ba7-e499-4ffa-8e39-7c8fe9543488@kernel.dk> (raw)
In-Reply-To: <Z9ytHt3tpEMsTcbN@kbusch-mbp>
On 3/20/25 6:04 PM, Keith Busch wrote:
> Sending a rebased pull: our trees were out of sync in the previous pull
> request.
>
> The following changes since commit fc22b34e95ce0a294c797c397a9db671e6ff4448:
>
> docs: sysfs-block: Clarify integrity sysfs attributes (2025-03-20 05:44:09 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.15-2025-03-20
>
> for you to fetch changes up to 64ea88e3afa8c5b6c3f9c477da304b7a56149612:
>
> nvmet: replace max(a, min(b, c)) by clamp(val, lo, hi) (2025-03-20 16:53:56 -0700)
>
> ----------------------------------------------------------------
> nvme updates for Linux 6.15
>
> - Secure concatenation for TCP transport (Hannes)
> - Multipath sysfs visibility (Nilay)
> - Various cleanups (Qasim, Baruch, Wang, Chen, Mike, Damien, Li)
> - Correct use of 64-bit BARs for pci-epf target (Niklas)
> - Socket fix for selinux when used in containers (Peijie)
Thanks Keith, pulled.
--
Jens Axboe
next prev parent reply other threads:[~2025-03-21 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 20:40 [GIT PULL] nvme updates for Linux 6.15 Keith Busch
2025-03-21 0:04 ` Keith Busch
2025-03-21 0:40 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-02 18:01 Keith Busch
2025-04-02 18:11 ` Jens Axboe
2025-04-10 15:01 Christoph Hellwig
2025-04-10 15:29 ` Jens Axboe
2025-04-10 15:40 ` 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=5d0f0ba7-e499-4ffa-8e39-7c8fe9543488@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