From: Andrew Morton <akpm@linux-foundation.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Mike Rapoport <rppt@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Arnd Bergmann <arnd@arndb.de>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Aleksandar Rikalo <arikalo@gmail.com>,
Dragan Mladjenovic <dragan.mladjenovic@syrmia.com>,
Chao-ying Fu <cfu@wavecomp.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Yinglu Yang <yangyinglu@loongson.cn>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Marc Zyngier <maz@kernel.org>,
linux-mips@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] MIPS: mm: Fix some memory-related issues
Date: Wed, 22 Nov 2023 10:29:00 -0800 [thread overview]
Message-ID: <20231122102900.68216218f77b61e342f37627@linux-foundation.org> (raw)
In-Reply-To: <20231122182419.30633-1-fancer.lancer@gmail.com>
On Wed, 22 Nov 2023 21:23:58 +0300 Serge Semin <fancer.lancer@gmail.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.
next prev parent reply other threads:[~2023-11-22 18:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 18:23 Serge Semin
2023-11-22 18:23 ` [PATCH 1/7] mips: dmi: Fix early remap on MIPS32 Serge Semin
2023-11-22 19:35 ` Arnd Bergmann
2023-11-23 9:32 ` Serge Semin
2023-11-23 12:13 ` Jiaxun Yang
2023-11-23 12:29 ` Thomas Bogendoerfer
2023-11-23 15:07 ` Jiaxun Yang
2023-11-23 16:07 ` Thomas Bogendoerfer
2023-11-23 17:33 ` Jiaxun Yang
2023-11-24 18:52 ` Serge Semin
2023-11-24 22:03 ` Jiaxun Yang
2023-11-27 16:23 ` Serge Semin
2023-11-27 21:08 ` Jiaxun Yang
2023-11-28 11:34 ` Serge Semin
2023-11-28 15:46 ` Jiaxun Yang
2023-11-30 19:16 ` Serge Semin
2023-12-01 0:13 ` Jiaxun Yang
2023-12-01 14:54 ` Serge Semin
2023-12-01 15:10 ` Jiaxun Yang
2023-12-01 18:26 ` Serge Semin
2023-11-28 12:41 ` Arnd Bergmann
2023-11-28 13:52 ` Serge Semin
2023-11-28 21:59 ` Arnd Bergmann
2023-11-30 19:26 ` Serge Semin
2023-11-24 22:34 ` Jiaxun Yang
2023-11-22 18:24 ` [PATCH 7/7] mips: Set dump-stack arch description Serge Semin
2023-11-22 18:29 ` Andrew Morton [this message]
2023-11-23 10:12 ` [PATCH 0/7] MIPS: mm: Fix some memory-related issues Serge Semin
[not found] ` <20231122182419.30633-7-fancer.lancer@gmail.com>
2023-11-23 10:06 ` [PATCH 6/7] mm/mm_init.c: Append '\n' to the unavailable ranges log-message Mike Rapoport
[not found] ` <20231122182419.30633-6-fancer.lancer@gmail.com>
2023-11-23 10:18 ` [PATCH 5/7] mm/mm_init.c: Extend init unavailable range doc info Mike Rapoport
[not found] ` <ehlzzv37o4exdn4smmu653wzjdotzdv3dhr3bduvemxssp37ro@sgegnyprquk4>
2023-11-24 8:19 ` Mike Rapoport
[not found] ` <h3g6ynqem6h6hefmdawzaspvzf4u5fwfh7rken3ogy5ucr5z5t@d5gagi2ql4ee>
2023-11-28 7:13 ` Mike Rapoport
[not found] ` <z6r4jvuo63deg5ezzrxiewuzgdfwvcluzp45r4gmu7vwx6fmlm@d5r6phck2ovh>
2023-11-29 6:14 ` Mike Rapoport
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=20231122102900.68216218f77b61e342f37627@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=aleksandar.rikalo@syrmia.com \
--cc=arikalo@gmail.com \
--cc=arnd@arndb.de \
--cc=cfu@wavecomp.com \
--cc=dragan.mladjenovic@syrmia.com \
--cc=fancer.lancer@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maz@kernel.org \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=willy@infradead.org \
--cc=yangtiezhu@loongson.cn \
--cc=yangyinglu@loongson.cn \
/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