Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 3 Oct 2022 13:22:49 -0700
From:   Jaegeuk Kim <jaegeuk@kernel.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Chao Yu <chao@kernel.org>,
        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: <YztEmSRnlVC+Wty4@google.com>
References: <20221004072013.3d2f395b@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221004072013.3d2f395b@canb.auug.org.au>
Precedence: bulk

On 10/04, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   5b4e447a70d1 ("f2fs: fix to account FS_CP_DATA_IO correctly")
> 
> Fixes tag
> 
>   Fixes: commit 040d2bb318d1 ("f2fs: fix to avoid deadloop if data_flush is on")
> 
> has these problem(s):
> 
>   - leading word 'commit' unexpected
> Fixes tag
> 
>   Fixes: commit 186857c5a14a ("f2fs: fix potential recursive call when enabling data_flush")
> 
> has these problem(s):
> 
>   - leading word 'commit' unexpected

Fixed. Thanks.

> 
> -- 
> Cheers,
> Stephen Rothwell