Linux block layer
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-block@vger.kernel.org
Subject: Re: integrity cleanups
Date: Wed, 26 Jun 2024 23:44:27 -0400	[thread overview]
Message-ID: <yq1h6dff3sq.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240626045950.189758-1-hch@lst.de> (Christoph Hellwig's message of "Wed, 26 Jun 2024 06:59:33 +0200")


Christoph,

> this series has a few cleanups to the block layer PI generation and
> verification code.

Looks OK to me.

Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2024-06-27  3:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  4:59 integrity cleanups Christoph Hellwig
2024-06-26  4:59 ` [PATCH 1/5] block: only zero non-PI metadata tuples in bio_integrity_prep Christoph Hellwig
2024-06-27 15:42   ` Kanchan Joshi
2024-06-26  4:59 ` [PATCH 2/5] block: simplify adding the payload " Christoph Hellwig
2024-06-27 15:42   ` Kanchan Joshi
2024-06-26  4:59 ` [PATCH 3/5] block: remove allocation failure warnings " Christoph Hellwig
2024-06-27 15:42   ` Kanchan Joshi
2024-06-26  4:59 ` [PATCH 4/5] block: switch on bio operation " Christoph Hellwig
2024-06-27 15:41   ` Kanchan Joshi
2024-06-26  4:59 ` [PATCH 5/5] block: remove bio_integrity_process Christoph Hellwig
2024-06-27 15:36   ` Kanchan Joshi
2024-06-27 15:47     ` Christoph Hellwig
2024-06-27 18:33       ` Kanchan Joshi
2024-06-28  6:02         ` Christoph Hellwig
2024-06-27  3:44 ` Martin K. Petersen [this message]
2024-06-28 16:30 ` integrity cleanups 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=yq1h6dff3sq.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    /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