From: James Hogan <james.hogan@imgtec.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: <linux-arch@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tglx@linutronix.de>, <arnd@arndb.de>,
Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>
Subject: Re: [RFC PATCH v1 26/31] ARC: Build system: Makefiles, Kconfig, Linker script
Date: Thu, 15 Nov 2012 17:49:57 +0000 [thread overview]
Message-ID: <50A52B45.6030907@imgtec.com> (raw)
In-Reply-To: <1352281674-2186-27-git-send-email-vgupta@synopsys.com>
Hi Vineet,
On 07/11/12 09:47, Vineet Gupta wrote:
> +config ARC
I just came across arch/mips/Kconfig which also defines ARC (and ARC32).
It's only used within arch/mips/, however it's probably more likely that
your ARC/CONFIG_ARC will find it's way into the generic bits of the
kernel which could get hit when the other ARC is defined.
Perhaps it's worth getting the other ARC renamed just in case?
Cheers
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, arnd@arndb.de,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [RFC PATCH v1 26/31] ARC: Build system: Makefiles, Kconfig, Linker script
Date: Thu, 15 Nov 2012 17:49:57 +0000 [thread overview]
Message-ID: <50A52B45.6030907@imgtec.com> (raw)
Message-ID: <20121115174957.NgveHIQxnLZaj0aeyvFPvhK4kJnjgoZZGJFr8wh9fsM@z> (raw)
In-Reply-To: <1352281674-2186-27-git-send-email-vgupta@synopsys.com>
Hi Vineet,
On 07/11/12 09:47, Vineet Gupta wrote:
> +config ARC
I just came across arch/mips/Kconfig which also defines ARC (and ARC32).
It's only used within arch/mips/, however it's probably more likely that
your ARC/CONFIG_ARC will find it's way into the generic bits of the
kernel which could get hit when the other ARC is defined.
Perhaps it's worth getting the other ARC renamed just in case?
Cheers
James
next parent reply other threads:[~2012-11-15 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1352281674-2186-1-git-send-email-vgupta@synopsys.com>
[not found] ` <1352281674-2186-27-git-send-email-vgupta@synopsys.com>
2012-11-15 17:49 ` James Hogan [this message]
2012-11-15 17:49 ` [RFC PATCH v1 26/31] ARC: Build system: Makefiles, Kconfig, Linker script James Hogan
2012-11-15 19:30 ` Ralf Baechle
2012-11-16 6:36 ` Vineet Gupta
2012-11-16 6:36 ` Vineet Gupta
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=50A52B45.6030907@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.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