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: linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL v2] nvme updates for Linux 6.19
Date: Thu, 4 Dec 2025 21:00:38 -0700	[thread overview]
Message-ID: <efff834b-2dd6-44b8-916d-24bc9b266050@kernel.dk> (raw)
In-Reply-To: <aTJQslM569DYXXkJ@kbusch-mbp>

> On Thu, Dec 04, 2025 at 03:53:35PM -0700, Keith Busch wrote:
>> Resending due to missing Sign-off-by tags in the previous revision.
>>
>> The following changes since commit d211a2803551c8ffdf0b97d129388f7d9cc129b5:
>>
>>   block/rnbd: correct all kernel-doc complaints (2025-12-01 07:19:50 -0700)
>>
>> are available in the Git repository at:
>>
>>   git://git.infradead.org/nvme.git tags/nvme-6.19-2025-12-04
>>
>> for you to fetch changes up to 13989207ee29c40501e719512e8dc90768325895:
>>
>>   nvme-fabrics: add ENOKEY to no retry criteria for authentication failures (2025-12-04 14:46:17 -0800)
>>
>> ----------------------------------------------------------------
>> nvme updates for Linux 6.19
>>
>>  - Subsystem usage cleanups (Max)
>>  - Endpoint device fixes (Shin'ichiro)
>>  - Debug statements (Gerd)
>>  - FC fabrics cleanups and fixes (Daniel)
>>  - Consistent alloc API usages (Israel)
>>  - Code comment updates (Chu)
>>  - Authentication retry fix (Justin)

Re-pulled, thanks.

-- 
Jens Axboe


      reply	other threads:[~2025-12-05  4:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 22:53 [GIT PULL v2] nvme updates for Linux 6.19 Keith Busch
2025-12-05  3:25 ` Keith Busch
2025-12-05  4:00   ` Jens Axboe [this message]

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=efff834b-2dd6-44b8-916d-24bc9b266050@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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