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, sagi@gimberg.me
Subject: Re: [GIT PULL] nvme updates for Linux 6.8
Date: Thu, 21 Dec 2023 14:48:34 -0700	[thread overview]
Message-ID: <ec6130a0-8718-4522-b7c2-1b2a3ec0b7f3@kernel.dk> (raw)
In-Reply-To: <ZYSwqV6e_iTw8jgV@kbusch-mbp.dhcp.thefacebook.com>

On 12/21/23 2:39 PM, Keith Busch wrote:
> This is the first nvme pull request for the upcoming Linux 6.8 merge
> window. There is a minor merge conflict when merging into Linus' master
> branch, and I've provided a reference resolution here:
> 
>   https://git.infradead.org/nvme.git/shortlog/refs/heads/nvme-6.8-merge
> 
> The following changes since commit 847c5bcdfb41704e52930783b028302f415a3209:
> 
>   block: skip QUEUE_FLAG_STATS and rq-qos for passthrough io (2023-12-01 18:29:18 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.8-2023-12-21
> 
> for you to fetch changes up to 5d51dc8db10190661232741c93a141bdfc05f5ee:
> 
>   nvme-fc: set numa_node after nvme_init_ctrl (2023-12-21 09:19:01 -0800)
> 
> ----------------------------------------------------------------
> nvme udpates for Linux 6.8
> 
>  - nvme fabrics spec updates (Guixin, Max)
>  - nvme target udpates (Guixin, Evan)
>  - nvme attribute refactoring (Daniel)
>  - nvme-fc numa fix (Keith)

Pulled (with typo fix in message), thanks!

-- 
Jens Axboe




      reply	other threads:[~2023-12-21 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 21:39 [GIT PULL] nvme updates for Linux 6.8 Keith Busch
2023-12-21 21:48 ` 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=ec6130a0-8718-4522-b7c2-1b2a3ec0b7f3@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@gimberg.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