All of lore.kernel.org
 help / color / mirror / Atom feed
From: jaegeuk@kernel.org
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jamie Iles <jamie@nuviainc.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, 14 Oct 2020 13:24:28 -0700	[thread overview]
Message-ID: <20201014202428.GA1536937@google.com> (raw)
In-Reply-To: <20201015071617.1f5ab26f@canb.auug.org.au>

Thanks,

I fixed it in f2fs-next branch.

Thanks,

On 10/15, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   e965857201e0 ("f2fs: wait for sysfs kobject removal before freeing f2fs_sb_info")
> 
> Fixes tag
> 
>   Fixes: bf9e697ecd4 ("f2fs: expose features to sysfs entry")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
>     or later) just making sure it is not set (or set to "auto").
> 
> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2020-10-14 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 20:16 linux-next: Fixes tag needs some work in the f2fs tree Stephen Rothwell
2020-10-14 20:24 ` jaegeuk [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-12-02 12:01 Stephen Rothwell
2020-12-03  5:44 ` Jaegeuk Kim
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=20201014202428.GA1536937@google.com \
    --to=jaegeuk@kernel.org \
    --cc=jamie@nuviainc.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.