linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, 23 Jun 2022 06:48:33 -0700	[thread overview]
Message-ID: <YrRvMdRIWC84FcAe@infradead.org> (raw)
In-Reply-To: <49f60048-1307-6860-794a-82020c9f2ffd@kernel.dk>

On Thu, Jun 23, 2022 at 07:44:08AM -0600, Jens Axboe wrote:
> On 6/23/22 7:23 AM, Christoph Hellwig wrote:
> > The following changes since commit 2645672ffe21f0a1c139bfbc05ad30fd4e4f2583:
> > 
> >   block: pop cached rq before potentially blocking rq_qos_throttle() (2022-06-21 10:59:58 -0600)
> > 
> > are available in the Git repository at:
> > 
> >   ssh://git.infradead.org/var/lib/git/nvme.git nvme-5.19
> 
> Usually I'd just turn that into the right git://, but it seems it's
> missing the signed tag this time too. Can you generate one?

Will do.

  reply	other threads:[~2022-06-23 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 13:23 [GIT PULL] nvmes fixes for Linux 5.19 Christoph Hellwig
2022-06-23 13:44 ` Jens Axboe
2022-06-23 13:48   ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-07 13:25 Christoph Hellwig
2022-07-07 23:38 ` Jens Axboe
2022-06-30 19:45 Christoph Hellwig
2022-06-30 20:16 ` Jens Axboe
2022-06-23 13:54 Christoph Hellwig
2022-06-23 13:55 ` Jens Axboe
2022-06-15 13:37 Christoph Hellwig
2022-06-15 15:39 ` Jens Axboe
2022-06-02  5:28 Christoph Hellwig
2022-06-02  7:49 ` Jens Axboe
2022-06-02  7:59   ` Christoph Hellwig
2022-06-02  8:05     ` 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=YrRvMdRIWC84FcAe@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).