From: Christoph Hellwig <hch@lst.de>
To: Heming Zhao <heming.zhao@suse.com>
Cc: song@kernel.org, guoqing.jiang@linux.dev, hch@lst.de,
linux-raid@vger.kernel.org, colyli@suse.de, hare@suse.de
Subject: Re: [PATCH] md/md-bitmap: fix incorrect usage for sb_index
Date: Fri, 23 Feb 2024 16:37:13 +0100 [thread overview]
Message-ID: <20240223153713.GA1366@lst.de> (raw)
In-Reply-To: <20240223121128.28985-1-heming.zhao@suse.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
... but if you're actually still actively using the bitmap code,
any chance you could try to look into updating it so that it doesn't
rely on ->bmap?
next prev parent reply other threads:[~2024-02-23 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:11 [PATCH] md/md-bitmap: fix incorrect usage for sb_index Heming Zhao
2024-02-23 15:37 ` Christoph Hellwig [this message]
2024-02-24 8:41 ` Heming Zhao
2024-02-26 11:04 ` Christoph Hellwig
2024-02-27 12:29 ` Heming Zhao
2024-02-26 21:43 ` Song Liu
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=20240223153713.GA1366@lst.de \
--to=hch@lst.de \
--cc=colyli@suse.de \
--cc=guoqing.jiang@linux.dev \
--cc=hare@suse.de \
--cc=heming.zhao@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=song@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;
as well as URLs for NNTP newsgroup(s).