From: Jens Axboe <axboe@kernel•dk>
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>
Subject: Re: linux-next: duplicate patch in the block tree
Date: Mon, 13 Mar 2023 15:59:48 -0600 [thread overview]
Message-ID: <9cd66e6e-6223-2fac-961e-f030c4424410@kernel.dk> (raw)
In-Reply-To: <20230314084625.3530839b@canb.auug.org.au>
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
next prev parent reply other threads:[~2023-03-13 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 21:46 linux-next: duplicate patch in the block tree Stephen Rothwell
2023-03-13 21:59 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-20 22:22 Stephen Rothwell
2025-05-11 21:40 Stephen Rothwell
2025-05-12 17:51 ` Jens Axboe
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=9cd66e6e-6223-2fac-961e-f030c4424410@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox