public inbox for linux-nvme@lists.infradead.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.13
Date: Thu, 5 Dec 2024 10:15:00 -0700	[thread overview]
Message-ID: <5b656b9b-2d3c-4ae0-8a73-6eaf1971ef62@kernel.dk> (raw)
In-Reply-To: <Z1HeockCWHXRcvGb@kbusch-mbp.dhcp.thefacebook.com>

On 12/5/24 10:10 AM, Keith Busch wrote:
> The following changes since commit ec9b3ac6e5630e320d926ea13a06d86d2a6bdde1:
> 
>   Merge tag 'nvme-6.13-2024-11-21' of git://git.infradead.org/nvme into for-6.13/block (2024-11-21 10:57:34 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.13-2024-12-05
> 
> for you to fetch changes up to b4e12f5728ff963ca5590c48b85a20d076bf517d:
> 
>   nvme-tcp: simplify nvme_tcp_teardown_io_queues() (2024-12-04 10:15:46 -0800)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.13
> 
>  - Target fix using incorrect zero buffer (Nilay)
>  - Device specifc deallocate quirk fixes (Christoph, Keith)
>  - Fabrics fix for handling max command target bugs (Maurizio)
>  - Cocci fix usage for kzalloc (Yu-Chen)
>  - DMA size fix for host memory buffer feature (Christoph)
>  - Fabrics queue cleanup fixes (Chunguang)

Pulled, thanks.

-- 
Jens Axboe



  reply	other threads:[~2024-12-05 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 17:10 [GIT PULL] nvme fixes for Linux 6.13 Keith Busch
2024-12-05 17:15 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-31 17:41 Keith Busch
2024-12-31 17:46 ` 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=5b656b9b-2d3c-4ae0-8a73-6eaf1971ef62@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