Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 14 Oct 2020 13:24:28 -0700
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
Message-ID: <20201014202428.GA1536937@google.com>
References: <20201015071617.1f5ab26f@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20201015071617.1f5ab26f@canb.auug.org.au>
Precedence: bulk

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