From: Thomas Schwinge <thomas@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: Migo-R (SH7722) vs. NUMA
Date: Thu, 08 Mar 2012 14:22:08 +0000 [thread overview]
Message-ID: <87vcmfmaun.fsf@schwinge.name> (raw)
In-Reply-To: <8762egpvhn.fsf@schwinge.name>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
Hi!
On Thu, 8 Mar 2012 00:04:28 -0800, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote:
> > > I forgot detail of MIGO-R.
> > > But in my quick check,
> > > my MIGO-R .config doesn't have CONFIG_NUMA since around v2.6.32-rc5
> >
> > Hmm, where do you see/check that?
> >
> > $ git blame -L /^CONFIG_NUMA/,+1 v3.2 -- arch/sh/configs/migor_defconfig
> > 70f784ec (Magnus Damm 2008-02-07 00:38:24 +0900 16) CONFIG_NUMA=y
>
> Ahh.. sorry for my confusion.
> It was not migor_defconfig.
> It is my local .config series which worked correctly on migo-r each linux version :)
> unfortunately (?) defconfig sometimes doesn't work...
I'm not an expert on this, but here is what I think should be done: a)
fix CONFIG_NUMA (apparently it used to work before the commit I
referenced in my original email), or b) tag it as broken/unsupported and
make sure it can't be enabled (and obviously don't enable it in the
default configuration). Which of the two is it?
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2012-03-08 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 10:15 Migo-R (SH7722) vs. NUMA Thomas Schwinge
2012-03-08 1:24 ` Kuninori Morimoto
2012-03-08 7:07 ` Thomas Schwinge
2012-03-08 8:04 ` Kuninori Morimoto
2012-03-08 14:22 ` Thomas Schwinge [this message]
2012-03-22 3:28 ` Paul Mundt
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=87vcmfmaun.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=linux-sh@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.