Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 fixes for Linux 6.12
Date: Wed, 25 Sep 2024 03:29:55 -0600	[thread overview]
Message-ID: <89e62f07-ad7a-4468-a519-b4f416a966fa@kernel.dk> (raw)
In-Reply-To: <ZvOwViViFuQSeyVk@kbusch-mbp>

On 9/25/24 12:40 AM, Keith Busch wrote:
> The following changes since commit 65f666c6203600053478ce8e34a1db269a8701c9:
> 
>   lib/sbitmap: define swap_lock as raw_spinlock_t (2024-09-20 00:20:06 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.12-2024-09-25
> 
> for you to fetch changes up to 9064610348b16356d43e59e286aedfec31825541:
> 
>   nvme: remove CC register read-back during enabling (2024-09-24 23:35:10 -0700)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.12
> 
>  - Multipath fixes (Hannes)
>  - Sysfs attribute list NULL terminate fix (Shin'ichiro)
>  - Remove problematic read-back (Keith)

Pulled, thanks.

-- 
Jens Axboe



  reply	other threads:[~2024-09-25  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  6:40 [GIT PULL] nvme fixes for Linux 6.12 Keith Busch
2024-09-25  9:29 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-31 15:08 Keith Busch
2024-10-31 15:10 ` Jens Axboe
2024-10-17 18:48 Keith Busch
2024-10-17 19:12 ` Jens Axboe
2024-09-13 14:34 [GIT PULL] nvme fixes for linux 6.12 Keith Busch
2024-09-13 14:39 ` 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=89e62f07-ad7a-4468-a519-b4f416a966fa@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