From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 5.12
Date: Fri, 12 Mar 2021 07:21:39 -0700 [thread overview]
Message-ID: <2a34717a-b5c5-0a3c-02b0-eb8a144aba15@kernel.dk> (raw)
In-Reply-To: <YEszeMEAQyfTPgHH@infradead.org>
On 3/12/21 2:25 AM, Christoph Hellwig wrote:
> The following changes since commit df66617bfe87487190a60783d26175b65d2502ce:
>
> block: rsxx: fix error return code of rsxx_pci_probe() (2021-03-10 08:25:37 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-5.12-2021-03-12
Pulled, thanks.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 5.12
Date: Fri, 12 Mar 2021 07:21:39 -0700 [thread overview]
Message-ID: <2a34717a-b5c5-0a3c-02b0-eb8a144aba15@kernel.dk> (raw)
In-Reply-To: <YEszeMEAQyfTPgHH@infradead.org>
On 3/12/21 2:25 AM, Christoph Hellwig wrote:
> The following changes since commit df66617bfe87487190a60783d26175b65d2502ce:
>
> block: rsxx: fix error return code of rsxx_pci_probe() (2021-03-10 08:25:37 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-5.12-2021-03-12
Pulled, thanks.
--
Jens Axboe
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-03-12 14:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 9:25 [GIT PULL] nvme fixes for 5.12 Christoph Hellwig
2021-03-12 9:25 ` Christoph Hellwig
2021-03-12 14:21 ` Jens Axboe [this message]
2021-03-12 14:21 ` Jens Axboe
2021-03-12 19:59 ` Christoph Hellwig
2021-03-12 19:59 ` Christoph Hellwig
2021-03-12 20:01 ` Jens Axboe
2021-03-12 20:01 ` Jens Axboe
2021-03-12 20:20 ` Christoph Hellwig
2021-03-12 20:20 ` Christoph Hellwig
2021-03-12 20:24 ` Jens Axboe
2021-03-12 20:24 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-03-19 7:14 Christoph Hellwig
2021-03-19 7:14 ` Christoph Hellwig
2021-03-19 12:41 ` Jens Axboe
2021-03-19 12:41 ` Jens Axboe
2021-03-05 16:11 Christoph Hellwig
2021-03-05 16:11 ` Christoph Hellwig
2021-03-05 16:13 ` Jens Axboe
2021-03-05 16:13 ` Jens Axboe
2021-03-04 17:59 Christoph Hellwig
2021-03-04 17:59 ` Christoph Hellwig
2021-03-04 20:26 ` Jens Axboe
2021-03-04 20:26 ` 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=2a34717a-b5c5-0a3c-02b0-eb8a144aba15@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--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.