From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists-infradead.org, linux-block@vger.kernel.org,
Keith Busch <kbusch@meta.com>,
hch@lst.de, martin.petersen@oracle.com, csander@purestorage.com
Subject: Re: [PATCHv8 0/2] block for-7.1/integrity rebase for mem alignment
Date: Mon, 23 Mar 2026 11:26:47 -0600 [thread overview]
Message-ID: <acF31yX6TyTprnyY@kbusch-mbp> (raw)
In-Reply-To: <f9c32e5a-ea3b-4a69-a269-ba1ebf474992@kernel.dk>
On Mon, Mar 23, 2026 at 11:23:35AM -0600, Jens Axboe wrote:
>
> You're looking in the wrong place. It's not in that branch, that branch
> only exists to have a merge point with the VFS. If you check my for-next
> branch you'll see it, and it's in for-7.1/block as well (that's the
> origin).
Oh my bad. My local branch was pointing at the vfs one from the rebase,
and I assumed that was the destination. I'm making new stuff on top and
was confused about the divergence. Thanks, and sorry for the noise.
next prev parent reply other threads:[~2026-03-23 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 14:46 [PATCHv8 0/2] block for-7.1/integrity rebase for mem alignment Keith Busch
2026-03-13 14:47 ` [PATCHv8 1/2] blk-integrity: support arbitrary buffer alignment Keith Busch
2026-03-13 14:47 ` [PATCHv8 2/2] ublk: report BLK_SPLIT_INTERVAL_CAPABLE Keith Busch
2026-03-14 14:14 ` [PATCHv8 0/2] block for-7.1/integrity rebase for mem alignment Jens Axboe
2026-03-23 17:12 ` Keith Busch
2026-03-23 17:14 ` Jens Axboe
2026-03-23 17:21 ` Keith Busch
2026-03-23 17:23 ` Jens Axboe
2026-03-23 17:26 ` Keith Busch [this message]
2026-03-23 17:27 ` 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=acF31yX6TyTprnyY@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=hch@lst.de \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists-infradead.org \
--cc=martin.petersen@oracle.com \
/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