All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Fengnan Chang <changfengnan@vivo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the f2fs tree
Date: Fri, 18 Mar 2022 08:10:29 +1100	[thread overview]
Message-ID: <20220318081029.55bb053b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 432 bytes --]

Hi all,

In commit

  3459538a3654 ("f2fs: fix compressed file start atomic write may cause data corruption")

Fixes tag

  Fixes: 7eab7a696827 ("f2fs: compress: remove unneeded read when rewrite whole

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-03-17 21:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 21:10 Stephen Rothwell [this message]
2022-03-18  1:27 ` linux-next: Fixes tag needs some work in the f2fs tree 常凤楠
  -- 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
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=20220318081029.55bb053b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=changfengnan@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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 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.