From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
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:23:35 -0600 [thread overview]
Message-ID: <f9c32e5a-ea3b-4a69-a269-ba1ebf474992@kernel.dk> (raw)
In-Reply-To: <acF2l2coqz2K3j-V@kbusch-mbp>
On 3/23/26 11:21 AM, Keith Busch wrote:
> On Mon, Mar 23, 2026 at 11:14:23AM -0600, Jens Axboe wrote:
>> On 3/23/26 11:12 AM, Keith Busch wrote:
>>> Did you forget to 'git push' this branch?
>>
>> I don't think so?
>>
>> commit 203247c5cb972af5d46bdb7d41ef40078048810b
>> Author: Keith Busch <kbusch@kernel.org>
>> AuthorDate: Fri Mar 13 07:47:00 2026 -0700
>> Commit: Jens Axboe <axboe@kernel.dk>
>> CommitDate: Sat Mar 14 07:44:30 2026 -0600
>>
>> blk-integrity: support arbitrary buffer alignment
>>
>> and
>>
>> commit 5d540162059598c3f79e12f96064825cc91f0f9c
>> Author: Caleb Sander Mateos <csander@purestorage.com>
>> AuthorDate: Fri Mar 13 07:47:01 2026 -0700
>> Commit: Jens Axboe <axboe@kernel.dk>
>> CommitDate: Sat Mar 14 07:44:30 2026 -0600
>>
>> ublk: report BLK_SPLIT_INTERVAL_CAPABLE
>>
>> in the tree since 9 days ago?
>
> The current gitweb doesn't show it:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git/log/?h=for-7.1/block-integrity
>
> And I don't find it in the repo either:
>
> $ git fetch block
> $ git log block/for-7.1/block-integrity -n 1
>
> commit a9aa6045abde87b94168c3ba034b953417e27272 (block/for-7.1/block-integrity)
> Author: Christoph Hellwig <hch@lst.de>
> Date: Mon Feb 23 05:20:07 2026 -0800
>
> block: pass a maxlen argument to bio_iov_iter_bounce
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).
--
Jens Axboe
next prev parent reply other threads:[~2026-03-23 17:23 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 [this message]
2026-03-23 17:26 ` Keith Busch
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=f9c32e5a-ea3b-4a69-a269-ba1ebf474992@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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