[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231122102900.68216218f77b61e342f37627@linux-foundation.org>
Date: Wed, 22 Nov 2023 10:29:00 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Serge Semin <fancer.lancer@...il.com>
Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Mike Rapoport <rppt@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
Arnd Bergmann <arnd@...db.de>,
Aleksandar Rikalo <aleksandar.rikalo@...mia.com>,
Aleksandar Rikalo <arikalo@...il.com>,
Dragan Mladjenovic <dragan.mladjenovic@...mia.com>,
Chao-ying Fu <cfu@...ecomp.com>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Yinglu Yang <yangyinglu@...ngson.cn>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
Marc Zyngier <maz@...nel.org>, linux-mips@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] MIPS: mm: Fix some memory-related issues
On Wed, 22 Nov 2023 21:23:58 +0300 Serge Semin <fancer.lancer@...il.com> wrote:
> Just recently I've rebased my MIPS32-related work from kernel 6.5-rc4 onto
> the latest kernel 6.7-rc1 and immediately got into a bootup-time
> mm-related bug (see patches 3-5 in this series). After fixing it I decided
> it was time to submit for review the generic MIPS code fixes which I have
> been collecting in my local repo for the last year. I was going to submit
> them a bit later after I finished working on a patchset with my SoC
> arch-specific changes, but since it was getting bigger and bigger, it
> turned to be reasonable to spill out the generic part of series right away
> especially seeing it might get to be useful in the most recent kernel.
It would have been better to separate out the two tiny unrelated MM
patches from this series. I'll steal them - if they later turn up via
the MIPS tree then that's OK.
Powered by blists - more mailing lists