From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>,
hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 6.14
Date: Mon, 3 Feb 2025 09:19:44 -0700 [thread overview]
Message-ID: <a609766c-3095-4354-8402-16ca047314b1@kernel.dk> (raw)
In-Reply-To: <Z6DavvYWWh5eWDjr@kbusch-mbp>
On 2/3/25 8:03 AM, Keith Busch wrote:
> [now with linux-nvme list copied]
>
> The following changes since commit e7b94c5c6f3b6435206f0e4ef7c5aa4eceae42f9:
>
> Merge tag 'md-6.14-20250113' of https://git.kernel.org/pub/scm/linux/kernel/git/mdraid/linux into for-6.14/block (2025-01-13 10:30:33 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.14-2025-01-31
>
> for you to fetch changes up to c8ed6cb5d37bc09c7e25e49a670e9fd1a3bd1dfa:
>
> nvme-fc: use ctrl state getter (2025-01-31 10:14:36 -0800)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.14
>
> - Connection fixes for fibre channel transport (Daniel)
> - Endian fixes (Keith, Christoph)
> - Cleanup fix for host memory buffer (Francis)
> - Platform specific power quirks (Georg)
> - Target memory leak (Sagi)
> - Use appropriate controller state accessor (Daniel)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-02-03 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:03 [GIT PULL] nvme fixes for Linux 6.14 Keith Busch
2025-02-03 16:19 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-21 0:07 Keith Busch
2025-02-21 0:45 ` Jens Axboe
2025-03-06 1:39 Keith Busch
2025-03-06 11:33 ` Jens Axboe
2025-03-13 15:31 Keith Busch
2025-03-13 15:42 ` 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=a609766c-3095-4354-8402-16ca047314b1@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 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.