[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxFhi1iJ2cFfKi04@ZenIV>
Date: Fri, 2 Sep 2022 02:51:07 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Zhang Yi <yi.zhang@...wei.com>
Cc: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, cluster-devel@...hat.com,
ntfs3@...ts.linux.dev, ocfs2-devel@....oracle.com,
reiserfs-devel@...r.kernel.org, jack@...e.cz, tytso@....edu,
akpm@...ux-foundation.org, axboe@...nel.dk, rpeterso@...hat.com,
agruenba@...hat.com, almaz.alexandrovich@...agon-software.com,
mark@...heh.com, dushistov@...l.ru, hch@...radead.org,
chengzhihao1@...wei.com, yukuai3@...wei.com
Subject: Re: [PATCH v2 13/14] ext2: replace bh_submit_read() helper with
bh_read_locked()
On Fri, Sep 02, 2022 at 09:32:53AM +0800, Zhang Yi wrote:
> On 2022/9/2 8:30, Al Viro wrote:
> > On Thu, Sep 01, 2022 at 09:35:04PM +0800, Zhang Yi wrote:
> >> bh_submit_read() and the uptodate check logic in bh_uptodate_or_lock()
> >> has been integrated in bh_read() helper, so switch to use it directly.
> >
> > s/bh_read_locked/bh_read/ in the summary?
> >
>
> Sorry, I don't get your question, I have already replace bh_read_locked()
> with bh_read() in the commit message, there is no bh_read_locked in the whole
> patch. Am I missing something?
Take a look at the subject ;-)
Powered by blists - more mailing lists