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.8
Date: Thu, 1 Feb 2024 09:11:31 -0700	[thread overview]
Message-ID: <ded9fdf2-7a68-473a-a748-c04472e7c6ef@kernel.dk> (raw)
In-Reply-To: <ZbvA5mjkhOpso5Nj@kbusch-mbp.dhcp.thefacebook.com>

On 2/1/24 9:03 AM, Keith Busch wrote:
> The following changes since commit 13f3956eb5681a4045a8dfdef48df5dc4d9f58a6:
> 
>   block: Fix WARNING in _copy_from_iter (2024-01-23 08:56:55 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.8-2024-02-01
> 
> for you to fetch changes up to 9f079dda14339ee87d864306a9dc8c6b4e4da40b:
> 
>   nvme: allow passthru cmd error logging (2024-02-01 07:44:53 -0800)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.8
> 
>  - Remove duplicated enums (Guixen)
>  - Use appropriate controller state accessors (Keith)
>  - Retryable authentication (Hannes)
>  - Add missing module descriptions (Chaitanya)
>  - Fibre-channel fixes for blktests (Daniel)
>  - Various type correctness updates (Caleb)
>  - Improve fabrics connection debugging prints (Nitin)
>  - Passthrough command verbose error logging (Adam)

Pulled, thanks.

-- 
Jens Axboe




  reply	other threads:[~2024-02-01 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 16:03 [GIT PULL] nvme fixes for Linux 6.8 Keith Busch
2024-02-01 16:11 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-08 21:26 Keith Busch
2024-02-08 22:05 ` Jens Axboe
2024-02-15 16:09 Keith Busch
2024-02-15 16:42 ` 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=ded9fdf2-7a68-473a-a748-c04472e7c6ef@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.