Message ID | YgTB0csAbKyI5WvN@infradead.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] nvme fixes for Linux 5.17 | expand |
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.
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?
On 2/22/22 10:21 AM, Christoph Hellwig wrote: > 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? Hmm? https://git.kernel.dk/cgit/linux-block/commit/?h=block-5.17&id=93e2c52d71a6067d08ee927e2682e9781cb911ef It also went upstream last week.
On Tue, Feb 22, 2022 at 10:26:16AM -0700, Jens Axboe wrote: > Hmm? > > https://git.kernel.dk/cgit/linux-block/commit/?h=block-5.17&id=93e2c52d71a6067d08ee927e2682e9781cb911ef Indeed. I somehow had a stale block-5.17 branch locally.