From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chao Yu <chao@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the f2fs tree
Date: Mon, 3 Oct 2022 13:22:49 -0700 [thread overview]
Message-ID: <YztEmSRnlVC+Wty4@google.com> (raw)
In-Reply-To: <20221004072013.3d2f395b@canb.auug.org.au>
On 10/04, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 5b4e447a70d1 ("f2fs: fix to account FS_CP_DATA_IO correctly")
>
> Fixes tag
>
> Fixes: commit 040d2bb318d1 ("f2fs: fix to avoid deadloop if data_flush is on")
>
> has these problem(s):
>
> - leading word 'commit' unexpected
> Fixes tag
>
> Fixes: commit 186857c5a14a ("f2fs: fix potential recursive call when enabling data_flush")
>
> has these problem(s):
>
> - leading word 'commit' unexpected
Fixed. Thanks.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2022-10-03 20:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 20:20 linux-next: Fixes tag needs some work in the f2fs tree Stephen Rothwell
2022-10-03 20:22 ` Jaegeuk Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-10 21:28 Stephen Rothwell
2022-10-28 4:32 Stephen Rothwell
2022-04-13 21:41 Stephen Rothwell
2022-04-13 21:58 ` Jaegeuk Kim
2022-03-17 21:10 Stephen Rothwell
2022-03-18 1:27 ` 常凤楠
2021-10-21 22:31 Stephen Rothwell
2021-10-21 22:35 ` Jaegeuk Kim
2020-12-02 12:01 Stephen Rothwell
2020-12-03 5:44 ` Jaegeuk Kim
2020-10-14 20:16 Stephen Rothwell
2020-10-14 20:24 ` jaegeuk
2020-06-05 0:04 Stephen Rothwell
2020-06-05 1:08 ` Jaegeuk Kim
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=YztEmSRnlVC+Wty4@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).