Message-ID: <9cd66e6e-6223-2fac-961e-f030c4424410@kernel.dk>
Date:   Mon, 13 Mar 2023 15:59:48 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Subject: Re: linux-next: duplicate patch in the block tree
Content-Language: en-US
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20230314084625.3530839b@canb.auug.org.au>
From:   Jens Axboe <axboe@kernel.dk>
In-Reply-To: <20230314084625.3530839b@canb.auug.org.au>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 3/13/23 3:46 PM, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>   6d114e22385b ("io_uring: silence variable ‘prev’ set but not used warning")
> 
> This is commit
> 
>   fa780334a8c3 ("io_uring: silence variable ‘prev’ set but not used warning")
> 
> in Linus' tree.

That's fine, it's just an older stale merge as I added the reviewed-by
tag before it went upstream. I'll rebase my for-next.

-- 
Jens Axboe