The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Muchun Song <muchun.song@linux.dev>,
	Muchun Song <songmuchun@bytedance.com>
Subject: Re: linux-next: manual merge of the liveupdate tree with the mm-unstable tree
Date: Wed, 29 Jul 2026 09:06:57 +0300	[thread overview]
Message-ID: <ammYgVd3Ty8JE0Fd@kernel.org> (raw)
In-Reply-To: <20260728134333.906cb26da4b6dec083b21344@linux-foundation.org>

On Tue, Jul 28, 2026 at 01:43:33PM -0700, Andrew Morton wrote:
> On Tue, 28 Jul 2026 20:38:54 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> 
> > I've got this for merging mm-unstable into liveupdate/next:
> > 
> > diff --cc mm/hugetlb.c
> > index ab4afc818e8cb,a77c3c1cb8943..0000000000000
> > --- a/mm/hugetlb.c
> > +++ b/mm/hugetlb.c
> 
> Well that's a pain.

Once resolved it stops being a pain :)

> I'll get the series "mm: Refactor bootmem gigantic
> hugepage allocation" into mm-stable in the next couple of days.  Can we
> then make this issue go away?

I can base the conflicting KHO work on mm-stable.
But if mm-stable is rebased we'd be in a bigger trouble.

Ideally we'd have a stable branch in mm tree that only contains "mm:
Refactor bootmem gigantic hugepage allocation" series and then this branch
would be easily merged into mm-stable and into liveupdate tree.

I'm going to keep liveupdate tree as it is for a couple of days and when
Pratyush sends the updated version we can resync again.

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2026-07-29  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 16:27 linux-next: manual merge of the liveupdate tree with the mm-unstable tree Mark Brown
2026-07-28 17:38 ` Mike Rapoport
2026-07-28 17:56   ` Mark Brown
2026-07-28 20:43   ` Andrew Morton
2026-07-29  6:06     ` Mike Rapoport [this message]
2026-07-29  7:10       ` Andrew Morton

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=ammYgVd3Ty8JE0Fd@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=songmuchun@bytedance.com \
    /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