public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 1 Aug 2025 08:30:54 -0400	[thread overview]
Message-ID: <aIyzfjoZuzN6G6o6@yury> (raw)
In-Reply-To: <20250801112727.17d6e604@canb.auug.org.au>

On Fri, Aug 01, 2025 at 11:27:27AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
> (all the commits in the bitmap tree)
> 
> The tree seems to have been rebased for no good reason.  Please clean
> it up.

Hi Stephen,

I didn't rebase it intentionally. Anyway, now the tree is rebased on
top of master. Hopefully it will clean the error.

Thanks,
YUry

  reply	other threads:[~2025-08-01 12:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01  1:27 linux-next: duplicate patches in the bitmap tree Stephen Rothwell
2025-08-01 12:30 ` Yury Norov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-08 23:08 Stephen Rothwell
2025-07-08 23:13 ` 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=aIyzfjoZuzN6G6o6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox