From: Paul Burton <paulburton@kernel.org>
To: Thomas Bogendoerfer <tbogendoerfer@suse.de>
Cc: Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: linux-mips@vger.kernel.org
Subject: Re: [PATCH 1/3] MIPS: SGI-IP27: Fix node_distance
Date: Thu, 09 Jan 2020 10:52:36 -0800 [thread overview]
Message-ID: <5e177675.1c69fb81.61ebf.5532@mx.google.com> (raw)
In-Reply-To: <20200109122331.4109-1-tbogendoerfer@suse.de>
Hello,
Thomas Bogendoerfer wrote:
> node_distance must return values starting from 10 up to 255. 10 means
> local, 255 unreachable.
Series applied to mips-next.
> MIPS: SGI-IP27: Fix node_distance
> commit a20ebc047a4a
> https://git.kernel.org/mips/c/a20ebc047a4a
>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
>
> MIPS: Loongson64: Fix node_distance()
> commit a14879e149c9
> https://git.kernel.org/mips/c/a14879e149c9
>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
>
> MIPS: mm: Place per_cpu on different nodes, if NUMA is enabled
> commit f3c560a61b4e
> https://git.kernel.org/mips/c/f3c560a61b4e
>
> Signed-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>
> Signed-off-by: Paul Burton <paulburton@kernel.org>
Thanks,
Paul
[ This message was auto-generated; if you believe anything is incorrect
then please email paulburton@kernel.org to report it. ]
prev parent reply other threads:[~2020-01-09 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:23 Thomas Bogendoerfer
2020-01-09 12:23 ` [PATCH 2/3] MIPS: Loongson64: Fix node_distance() Thomas Bogendoerfer
2020-01-09 12:23 ` [PATCH 3/3] MIPS: mm: Place per_cpu on different nodes, if NUMA is enabled Thomas Bogendoerfer
2020-01-09 18:52 ` Paul Burton [this message]
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=5e177675.1c69fb81.61ebf.5532@mx.google.com \
--to=paulburton@kernel.org \
--cc=tbogendoerfer@suse.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
all inboxes | Powered by JetHome®