All of 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.11
Date: Thu, 5 Sep 2024 08:46:39 -0600	[thread overview]
Message-ID: <d3c72088-e0da-4582-978a-5230c32af9e9@kernel.dk> (raw)
In-Reply-To: <ZtnC_xT5S0X2ZuZB@kbusch-mbp>

On 9/5/24 8:41 AM, Keith Busch wrote:
> The following changes since commit e6b09a173870720e4d4c6fd755803970015ac043:
> 
>   Merge tag 'nvme-6.11-2024-08-22' of git://git.infradead.org/nvme into block-6.11 (2024-08-22 16:20:24 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.11-2024-09-05
> 
> for you to fetch changes up to 899d2e5a4e3d36689e8938e152f4b69a4bcc6b4d:
> 
>   nvmet: Identify-Active Namespace ID List command should reject invalid nsid (2024-09-03 10:05:40 -0700)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.11
> 
>  - Sparse fix on static symbol (Jinjie)
>  - Misleading warning message fix (Keith)
>  - TCP command allocation handling fix (Maurizio)
>  - PCI tagset allocation handling fix (Keith)
>  - Low-power quirk for Samsung (Georg)
>  - Queue limits fix for zone devices (Christoph)
>  - Target protocol behavior fix (Maurizio)

Pulled, thanks.

-- 
Jens Axboe




  reply	other threads:[~2024-09-05 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 14:41 [GIT PULL] nvme fixes for Linux 6.11 Keith Busch
2024-09-05 14:46 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-22 20:36 Keith Busch
2024-08-22 22:38 ` Jens Axboe
2024-08-08 18:15 Keith Busch
2024-08-08 18:28 ` Jens Axboe
2024-07-26 14:04 Keith Busch
2024-07-26 14:06 ` 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=d3c72088-e0da-4582-978a-5230c32af9e9@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.