From: Yury Norov <yury.norov@gmail.com>
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 patches in the bitmap tree
Date: Tue, 8 Jul 2025 19:13:49 -0400 [thread overview]
Message-ID: <aG2mLfL2roOvK3zq@yury> (raw)
In-Reply-To: <20250709090842.467cfcfb@canb.auug.org.au>
On Wed, Jul 09, 2025 at 09:08:42AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> d702b0ed6329 ("MAINTAINERS: bitmap: add UAPI headers")
> adb5c828d022 ("uapi: bitops: use UAPI-safe variant of BITS_PER_LONG again (2)")
>
> These are commits
>
> 1afc85deecd3 ("MAINTAINERS: bitmap: add UAPI headers")
> 70b9c0c11e55 ("uapi: bitops: use UAPI-safe variant of BITS_PER_LONG again (2)")
>
> in Linus' tree.
Fixed. Thanks.
next prev parent reply other threads:[~2025-07-08 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 23:08 linux-next: duplicate patches in the bitmap tree Stephen Rothwell
2025-07-08 23:13 ` Yury Norov [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-01 1:27 Stephen Rothwell
2025-08-01 12:30 ` Yury Norov
2023-02-09 2:02 Stephen Rothwell
2023-02-09 2:22 ` Yury Norov
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=aG2mLfL2roOvK3zq@yury \
--to=yury.norov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.