public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
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:12:08 -0600	[thread overview]
Message-ID: <acF0aJa-GXGYPqS0@kbusch-mbp> (raw)
In-Reply-To: <177349768999.37164.10048861817413145882.b4-ty@kernel.dk>

On Sat, Mar 14, 2026 at 08:14:49AM -0600, Jens Axboe wrote:
> On Fri, 13 Mar 2026 07:46:59 -0700, Keith Busch wrote:
> > This is the rebased version of the flexible t10 alignment feature on top
> > of block's for-7.1/block-integrity branch to apply atop Christoph's
> > fs-integrity:
> > 
> >   https://lore.kernel.org/linux-block/20260223132021.292832-1-hch@lst.de/
> > 
> > The only change from the previous version is to incorporate the function
> > name changes and verify's status code return type that were introduced
> > in the file system integrity support patch set.
> > 
> > [...]
> 
> Applied, thanks!

Did you forget to 'git push' this branch?

  reply	other threads:[~2026-03-23 17:12 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 [this message]
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
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=acF0aJa-GXGYPqS0@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