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.10
Date: Wed, 29 May 2024 19:55:07 -0600	[thread overview]
Message-ID: <ff000445-6ad0-4977-b407-36e74adc1dc4@kernel.dk> (raw)
In-Reply-To: <Zlen3slew1w4dneo@kbusch-mbp.dhcp.thefacebook.com>

On 5/29/24 4:10 PM, Keith Busch wrote:
> The following changes since commit f0eab3e8d1530b87f3523cee060004dd513a6d2b:
> 
>   block: t10-pi: add MODULE_DESCRIPTION() (2024-05-20 08:07:44 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.10-2024-05-29
> 
> for you to fetch changes up to c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4:
> 
>   nvmet: fix a possible leak when destroy a ctrl during qp establishment (2024-05-28 10:01:52 -0700)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.10
> 
>  - Removing unused fields (Kanchan)
>  - Large folio offsets support (Kundan)
>  - Multipath NUMA node initialiazation fix (Nilay)
>  - Multipath IO stats accounting fixes (Keith)
>  - Circular lockdep fix (Keith)
>  - Target race condition fix (Sagi)
>  - Target memory leak fix (Sagi)

Pulled, thanks.

-- 
Jens Axboe




  reply	other threads:[~2024-05-30  1:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 22:10 [GIT PULL] nvme fixes for Linux 6.10 Keith Busch
2024-05-30  1:55 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-05 18:10 Keith Busch
2024-06-05 18:13 ` Jens Axboe
2024-06-27 18:03 Keith Busch
2024-06-27 18:15 ` 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=ff000445-6ad0-4977-b407-36e74adc1dc4@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