All of lore.kernel.org
 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] nvme fixes for Linux 5.17
Date: Tue, 22 Feb 2022 09:21:10 -0800	[thread overview]
Message-ID: <YhUbhsy+C7Q16ihM@infradead.org> (raw)
In-Reply-To: <d165d411-4499-12aa-fb59-05ff1e2faaa2@kernel.dk>

On Thu, Feb 10, 2022 at 06:57:10AM -0700, Jens Axboe wrote:
> On 2/10/22 12:42 AM, Christoph Hellwig wrote:
> > The following changes since commit b13e0c71856817fca67159b11abac350e41289f5:
> > 
> >   block: bio-integrity: Advance seed correctly for larger interval sizes (2022-02-03 21:09:24 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.infradead.org/nvme.git tags/nvme-5.17-2022-02-10
> 
> Pulled, thanks.

Looks like it isn't in the block-5.17 branch any more.  Should I
just resend it for this week?

  reply	other threads:[~2022-02-22 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  7:42 [GIT PULL] nvme fixes for Linux 5.17 Christoph Hellwig
2022-02-10 13:57 ` Jens Axboe
2022-02-22 17:21   ` Christoph Hellwig [this message]
2022-02-22 17:26     ` Jens Axboe
2022-02-22 17:29       ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2022-02-24  7:33 Christoph Hellwig
2022-02-24 14:03 ` Jens Axboe
2022-02-03 19:35 Christoph Hellwig
2022-02-03 19:38 ` Jens Axboe
2022-01-27  7:19 Christoph Hellwig
2022-01-27 13:53 ` 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=YhUbhsy+C7Q16ihM@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 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.