From: Kanchan Joshi <joshi.k@samsung.com>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Yu Kuai <yukuai3@huawei.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
linux-raid@vger.kernel.org, target-devel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 3/3] block: split struct bio_integrity_payload
Date: Wed, 26 Feb 2025 15:23:11 +0530 [thread overview]
Message-ID: <5ac8aa8d-e1de-44e6-831f-c25f2d7791ab@samsung.com> (raw)
In-Reply-To: <20250225154449.422989-4-hch@lst.de>
On 2/25/2025 9:14 PM, Christoph Hellwig wrote:
> Reduce struct bio_integrity_payload to the minimal structure needed in
> common code and create two separate containing structures for the
> automatically generated payload and the caller allocated payload.
> The latter is a simple wrapper for struct bio_integrity_payload and
> the bvecs, while the former contains the additional fields moved out
> of strut bio_integrity_payload.
nit: s/strut/struct
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
next prev parent reply other threads:[~2025-02-26 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 15:44 split out the auto-PI code and data structures v2 Christoph Hellwig
2025-02-25 15:44 ` [PATCH 1/3] block: mark bounce buffering as incompatible with integrity Christoph Hellwig
2025-02-25 15:44 ` [PATCH 2/3] block: move the block layer auto-integrity code into a new file Christoph Hellwig
2025-02-25 15:44 ` [PATCH 3/3] block: split struct bio_integrity_payload Christoph Hellwig
2025-02-26 9:53 ` Kanchan Joshi [this message]
2025-02-26 12:10 ` Anuj gupta
2025-02-26 14:38 ` split out the auto-PI code and data structures v2 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=5ac8aa8d-e1de-44e6-831f-c25f2d7791ab@samsung.com \
--to=joshi.k@samsung.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=yukuai3@huawei.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