From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jack Qiu <jack.qiu@huawei.com>,
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: Wed, 2 Dec 2020 21:44:04 -0800 [thread overview]
Message-ID: <X8h7JPsjS/wlQDsY@google.com> (raw)
In-Reply-To: <20201202230159.17045522@canb.auug.org.au>
On 12/02, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 32c202c563c7 ("f2fs: init dirty_secmap incorrectly")
>
> Fixes tag
>
> Fixes: da52f8ade40b ("f2fs: get the right gc victim section when section
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over more than one line.
Oh, fixed the wrong commit message. :(
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2020-12-03 5:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 12:01 linux-next: Fixes tag needs some work in the f2fs tree Stephen Rothwell
2020-12-03 5:44 ` 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-10-03 20:20 Stephen Rothwell
2022-10-03 20:22 ` Jaegeuk Kim
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-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=X8h7JPsjS/wlQDsY@google.com \
--to=jaegeuk@kernel.org \
--cc=jack.qiu@huawei.com \
--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 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.