From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 6/8] btrfs: raid56: store a physical address in structure sector_ptr
Date: Mon, 21 Apr 2025 13:44:16 +0200 [thread overview]
Message-ID: <20250421114416.GA23431@lst.de> (raw)
In-Reply-To: <03dbeaa8ac424885402a6590e393a15d5ae67c82.1745024799.git.wqu@suse.com>
On Sat, Apr 19, 2025 at 04:47:13PM +0930, Qu Wenruo wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> [ Use physical addresses instead to handle highmem. ]
> Signed-off-by: Qu Wenruo <wqu@suse.com>
I think you should take full credit and authorship here as this is quite
different from what I posted.
The changes look good to me, though:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-04-21 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-19 7:17 [PATCH v2 0/8] btrfs: do not poking into the implementation details of bio_vec Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 1/8] btrfs: remove the alignment checks in end_bbio_data_read Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 2/8] btrfs: track the next file offset in struct btrfs_bio_ctrl Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 3/8] btrfs: pass a physical address to btrfs_repair_io_failure Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 4/8] btrfs: move kmapping out of btrfs_check_sector_csum Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 5/8] btrfs: simplify bvec iteration in index_one_bio Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 6/8] btrfs: raid56: store a physical address in structure sector_ptr Qu Wenruo
2025-04-21 11:44 ` Christoph Hellwig [this message]
2025-04-22 11:31 ` David Sterba
2025-04-23 9:40 ` Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 7/8] btrfs: scrub: use virtual addresses directly Qu Wenruo
2025-04-19 7:17 ` [PATCH v2 8/8] btrfs: use bvec_kmap_local in btrfs_decompress_buf2page Qu Wenruo
2025-04-21 13:29 ` [PATCH v2 0/8] btrfs: do not poking into the implementation details of bio_vec Josef Bacik
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=20250421114416.GA23431@lst.de \
--to=hch@lst.de \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.