From: Jinyang He <hejinyang@loongson.cn>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Huacai Chen <chenhc@lemote.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] memory node
Date: Thu, 3 Dec 2020 16:57:45 +0800 [thread overview]
Message-ID: <1606985867-9791-1-git-send-email-hejinyang@loongson.cn> (raw)
*** BLURB HERE ***
Jinyang He (2):
MIPS: Remove unused memblock_set_node
MIPS: Add fix_range_node after parse "mem=" parameter
arch/mips/include/asm/bootinfo.h | 1 +
arch/mips/kernel/setup.c | 9 +++++----
arch/mips/loongson64/numa.c | 11 +++++++++++
3 files changed, 17 insertions(+), 4 deletions(-)
--
2.1.0
next reply other threads:[~2020-12-03 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 8:57 Jinyang He [this message]
2020-12-03 8:57 ` [PATCH 1/2] MIPS: Remove unused memblock_set_node Jinyang He
2020-12-03 8:57 ` [PATCH 2/2] MIPS: Add fix_range_node after parse "mem=" parameter Jinyang He
2020-12-03 9:27 ` Jiaxun Yang
2020-12-03 9:55 ` Jinyang He
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=1606985867-9791-1-git-send-email-hejinyang@loongson.cn \
--to=hejinyang@loongson.cn \
--cc=chenhc@lemote.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).