From: Andreas Gruenbacher <agruenba@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] gfs2: Remove use of error flag in journal reads
Date: Thu, 21 Dec 2023 13:38:05 +0100 [thread overview]
Message-ID: <CAHc6FU5Wn8NYn96SXyeWq5ifHnO9GChqcbDX5x2ebQaKKfvJYg@mail.gmail.com> (raw)
In-Reply-To: <ZYMQx2070yb9Vkgs@casper.infradead.org>
On Wed, Dec 20, 2023 at 5:05 PM Matthew Wilcox <willy@infradead.org> wrote:
> On Wed, Dec 06, 2023 at 07:58:06PM +0000, Matthew Wilcox (Oracle) wrote:
> > Conventionally we use the uptodate bit to signal whether a read
> > encountered an error or not. Use folio_end_read() to set the uptodate
> > bit on success. Also use filemap_set_wb_err() to communicate the errno
> > instead of the more heavy-weight mapping_set_error().
>
> Ping?
Pushed to for-next now. Thanks for the patch and reminder.
Andreas
prev parent reply other threads:[~2023-12-21 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 19:58 [PATCH] gfs2: Remove use of error flag in journal reads Matthew Wilcox (Oracle)
2023-12-20 16:05 ` Matthew Wilcox
2023-12-21 12:38 ` Andreas Gruenbacher [this message]
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=CAHc6FU5Wn8NYn96SXyeWq5ifHnO9GChqcbDX5x2ebQaKKfvJYg@mail.gmail.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).