From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 6.2
Date: Wed, 15 Feb 2023 20:25:42 -0700 [thread overview]
Message-ID: <4c2ddb31-b384-2d39-e49e-2f6683062f01@kernel.dk> (raw)
In-Reply-To: <Y+0hG6t1gTse7yfo@infradead.org>
On 2/15/23 11:14 AM, Christoph Hellwig wrote:
> The following changes since commit 38c33ece232019c5b18b4d5ec0254807cac06b7c:
>
> Merge tag 'nvme-6.2-2023-02-09' of git://git.infradead.org/nvme into block-6.2 (2023-02-09 08:12:06 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.2-2023-02-15
>
> for you to fetch changes up to dc785d69d753a3894c93afc23b91404652382ead:
>
> nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev (2023-02-14 06:39:02 +0100)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.2
>
> - always return an ERR_PTR from nvme_pci_alloc_dev (Irvin Cote)
> - add bogus ID quirk for ADATA SX6000PNP (Daniel Wagner)
> - set the DMA mask earlier (Christoph Hellwig)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2023-02-16 3:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 18:14 [GIT PULL] nvme fixes for Linux 6.2 Christoph Hellwig
2023-02-16 3:25 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-09 5:10 Christoph Hellwig
2023-02-09 15:12 ` Jens Axboe
2023-02-02 15:23 Christoph Hellwig
2023-02-02 18:02 ` Jens Axboe
2023-01-26 17:38 Christoph Hellwig
2023-01-26 18:44 ` Jens Axboe
2023-01-20 5:52 Christoph Hellwig
2023-01-20 15:09 ` Jens Axboe
2023-01-12 8:25 Christoph Hellwig
2023-01-12 17:37 ` Jens Axboe
2022-12-29 16:41 Christoph Hellwig
2022-12-29 18:32 ` Jens Axboe
2022-12-22 15:43 Christoph Hellwig
2022-12-22 16:23 ` 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=4c2ddb31-b384-2d39-e49e-2f6683062f01@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.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.