linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: at-91: ARCH_AT91SAM9X5 went missing
Date: Thu, 14 Mar 2013 09:30:16 +0100	[thread overview]
Message-ID: <51418A98.3050009@atmel.com> (raw)
In-Reply-To: <1363249052.1335.32.camel@x61.thuisdomein>

On 03/14/2013 09:17 AM, Paul Bolle :
> On Wed, 2013-03-13 at 13:26 +0100, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
>> but the ARCH_AT91SAM9x5 never exist at the mainline
> 
> I'm not sure I understand this.
> 
> We're discussing the effects of commit
> 1e3ce2b8545390a2aee8dbfcd49ca4161b636000 ("AR[M]: at91: introduce
> SOC_AT91xxx define to allow to compile SoC core support") here. It did
> remove ARCH_AT91SAM9X5:
>     $ git show 1e3ce2b8545390a2aee8dbfcd49ca4161b636000 | grep ARCH_AT91SAM9X5
>     -config ARCH_AT91SAM9X5
>     @@ -93,8 +91,47 @@ config ARCH_AT91SAM9X5
>     -obj-$(CONFIG_ARCH_AT91SAM9X5)	+= at91sam9x5.o
>     -#ifdef CONFIG_ARCH_AT91SAM9X5
>     -#if !defined(CONFIG_ARCH_AT91SAM9X5)
> 
> It also added SOC_AT91SAM9X5, and that symbol even triggers the
> compilation of a file named at91sam9x5.c:
>     $ git show 1e3ce2b8545390a2aee8dbfcd49ca4161b636000 | grep SOC_AT91SAM9X5
>     +config SOC_AT91SAM9X5
>     +obj-$(CONFIG_SOC_AT91SAM9X5)	+= at91sam9x5.o
>     +#ifdef CONFIG_SOC_AT91SAM9X5
>     +#if !defined(CONFIG_SOC_AT91SAM9X5)
> 
> And also note that ARCH_AT91SAM9X5 still is used as an (optional) dependency:
>     $ git grep -n ARCH_AT91SAM9X5 v3.9-rc2
>     v3.9-rc2:drivers/net/can/Kconfig:68:    depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9X5

Which is removed by patch:
"[PATCH v2 2/2] can: Kconfig: CAN_AT91 depends on ARM"

It should appear in CAN git tree soon.

Best regards,
-- 
Nicolas Ferre

  reply	other threads:[~2013-03-14  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 10:48 ARM: at-91: ARCH_AT91SAM9X5 went missing Paul Bolle
2013-03-13 11:12 ` Nicolas Ferre
2013-03-13 11:22   ` Paul Bolle
2013-03-13 12:26     ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-14  8:17       ` Paul Bolle
2013-03-14  8:30         ` Nicolas Ferre [this message]
2013-03-14  8:52           ` Paul Bolle
2013-03-13 12:30     ` Nicolas Ferre

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=51418A98.3050009@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).