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: linux-nvme@lists.infradead.org, hch@lst.de
Subject: Re: [GIT PULL] nvme fixes for 6.7
Date: Wed, 8 Nov 2023 09:20:20 -0700	[thread overview]
Message-ID: <b7624859-fe70-4f59-8aa3-8bd00307dd04@kernel.dk> (raw)
In-Reply-To: <ZUu0J09yJmK72bKa@kbusch-mbp.dhcp.thefacebook.com>

On 11/8/23 9:15 AM, Keith Busch wrote:
> The following changes since commit d2f51b3516dade79269ff45eae2a7668ae711b25:
> 
>   Merge tag 'rtc-6.7' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux (2023-11-05 18:49:40 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.7-2023-11-8
> 
> for you to fetch changes up to 706add13676da7ad213b65e92b94af5efc8c4131:
> 
>   nvme: keyring: fix conditional compilation (2023-11-08 08:07:08 -0800)
> 
> ----------------------------------------------------------------
> nvme fixes for 6.7
> 
>  - nvme keyring config compile fixes (Hannes and Arnd)
>  - fabrics keep alive fixes (Hannes)
>  - tcp authentication fixes (Mark)
>  - io_uring_cmd error handling fix (Anuj)
>  - stale firmware attribute fix (Daniel)
>  - tcp memory leak (Christophe)
>  - cytpo library usage simplification (Eric)

Pulled, thanks.

-- 
Jens Axboe



  reply	other threads:[~2023-11-08 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 16:15 [GIT PULL] nvme fixes for 6.7 Keith Busch
2023-11-08 16:20 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-22 16:27 Keith Busch
2023-11-22 17:19 ` 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=b7624859-fe70-4f59-8aa3-8bd00307dd04@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --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