Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

From: Richard Weinberger <richard@nod.at>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 Stephen Rothwell <sfr@canb.auug.org.au>,
	 kent overstreet <kent.overstreet@linux.dev>,
	 SeongJae Park <sj@kernel.org>,
	 anton ivanov <anton.ivanov@cambridgegreys.com>,
	 Johannes Berg <johannes@sipsolutions.net>,
	 linux-mm <linux-mm@kvack.org>,
	 linux-um <linux-um@lists.infradead.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc
Date: Mon, 22 Apr 2024 22:50:00 +0200 (CEST)	[thread overview]
Message-ID: <714170984.15180.1713819000411.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAJuCfpFsrQxa2CX66xQtxp=Y-=R5_YkJMMX9VQ-g32rdCrukeg@mail.gmail.com>

----- Ursprüngliche Mail -----
> Von: "Suren Baghdasaryan" <surenb@google.com>
>> > It's in mm-unstable under dc26c7e79daf2fc11169b23c150862f0e878ee5a. I
>> > think it just didn't reach Linus' tree yet.
>>
>> Hmm, so we better postpone this path until said commit hits Linus tree,
>> or you carry it together with the commit in mm-unstable.
> 
> Oh, sorry, I didn't realize you were talking about the `Fixes:
> 576477564ede` part... Yeah, unfortunately SHAs in mm-unstable are
> unstable, so the change being fixed is under
> edf0a25633bda1e5b7844478dd13b4326a3d5d09 now. I think Andrew placed
> this fix right after the change it fixes with intention to merge them
> together later on.

Ah, the patch itself goes via Andrew's tree, works for me!
Let me note this in the uml patchwork system.

Acked-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard