All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daeho Jeong <daehojeong@google.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: Thu, 21 Oct 2021 15:35:17 -0700	[thread overview]
Message-ID: <YXHrJWThIgUF/DJC@google.com> (raw)
In-Reply-To: <20211022093145.3b816875@canb.auug.org.au>

On 10/22, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   701179c15976 ("f2fs: include non-compressed blocks in compr_written_block")
> 
> Fixes tag
> 
>   Fixes: commit 5ac443e26a09 ("f2fs: add sysfs nodes to get runtime compression stat")
> 
> has these problem(s):
> 
>   - leading word 'commit' unexpected

Fixed. Thanks.

> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2021-10-21 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21 22:31 linux-next: Fixes tag needs some work in the f2fs tree Stephen Rothwell
2021-10-21 22:35 ` 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 ` 常凤楠
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=YXHrJWThIgUF/DJC@google.com \
    --to=jaegeuk@kernel.org \
    --cc=daehojeong@google.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.