From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
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 00:59:03 -0700 [thread overview]
Message-ID: <Yphtx84vMpkX+bsb@infradead.org> (raw)
In-Reply-To: <2ae24afc-6474-60f3-ece0-fb5a1d19f8c5@kernel.dk>
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
next prev parent reply other threads:[~2022-06-02 7:59 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 [this message]
2022-06-02 8:05 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
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=Yphtx84vMpkX+bsb@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).