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:   Wed, 23 Nov 2022 13:09:23 +0100
From:   David Sterba <dsterba@suse.cz>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Boris Burkov <boris@bur.io>,
        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 btrfs tree
Message-ID: <20221123120923.GK5824@suse.cz>
Reply-To: dsterba@suse.cz
References: <20221123081726.140b18d1@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221123081726.140b18d1@canb.auug.org.au>
User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Precedence: bulk

On Wed, Nov 23, 2022 at 08:17:26AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   e60fd7bf12f2 ("btrfs: fix improper error handling in btrfs_unlink")
> 
> Fixes tag
> 
>   Fixes: 6a1d44efb9d0 ("btrfs: setup qstr from dentrys using fscrypt helper")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: aa8270bea38f ("btrfs: setup qstr from dentrys using fscrypt helper")

Thanks, I thought I had squashed the commit e60fd7bf12f2, but apparently
not so the original reference became stale. Now fixed.