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] nvmes fixes for Linux 5.19
Date: Thu, 2 Jun 2022 02:05:39 -0600 [thread overview]
Message-ID: <f333ef06-6aab-81cb-e998-44b91670f9ef@kernel.dk> (raw)
In-Reply-To: <Yphtx84vMpkX+bsb@infradead.org>
On 6/2/22 1:59 AM, Christoph Hellwig wrote:
> On Thu, Jun 02, 2022 at 01:49:09AM -0600, Jens Axboe wrote:
>> On 6/1/22 11:28 PM, Christoph Hellwig wrote:
>>> The following changes since commit a1a2d8f0162b27e85e7ce0ae6a35c96a490e0559:
>>>
>>> bcache: avoid unnecessary soft lockup in kworker update_writeback_rate() (2022-05-28 06:48:26 -0600)
>>>
>>> are available in the Git repository at:
>>>
>>> ssh://git.infradead.org/var/lib/git/nvme.git tags/nvme-5.19-2022-06-02
>>
>> Eh, I can't pull from that... I used the usual git url with this tag.
>
> Sorry, that was my push url. The external facing one is:
>
> git://git.infradead.org/nvme.git tags/nvme-5.19-2022-06-02
Yep that's what I used, and matches what it should look like. All queued
up.
--
Jens Axboe
next prev parent reply other threads:[~2022-06-02 8:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 5:28 [GIT PULL] nvmes fixes for Linux 5.19 Christoph Hellwig
2022-06-02 7:49 ` Jens Axboe
2022-06-02 7:59 ` Christoph Hellwig
2022-06-02 8:05 ` Jens Axboe [this message]
2022-06-15 13:37 Christoph Hellwig
2022-06-15 15:39 ` Jens Axboe
2022-06-23 13:23 Christoph Hellwig
2022-06-23 13:44 ` Jens Axboe
2022-06-23 13:48 ` Christoph Hellwig
2022-06-23 13:54 Christoph Hellwig
2022-06-23 13:55 ` Jens Axboe
2022-06-30 19:45 Christoph Hellwig
2022-06-30 20:16 ` Jens Axboe
2022-07-07 13:25 Christoph Hellwig
2022-07-07 23:38 ` 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=f333ef06-6aab-81cb-e998-44b91670f9ef@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.