public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Third Round of Renesas ARM Based SoC Soc Updates for v3.18
Date: Tue, 09 Sep 2014 17:20:11 +0200	[thread overview]
Message-ID: <4196537.hvL3OIMxQq@wuerfel> (raw)
In-Reply-To: <cover.1410235571.git.horms+renesas@verge.net.au>

On Tuesday 09 September 2014 13:22:17 Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
> 
> Please consider these third round of Renesas ARM based SoC soc updates for v3.18.
> 
> This pull request is based on the previous round of
> such requests, tagged as renesas-soc2-for-v3.18,
> which you have already pulled.
> 
> This pull-request has a minor conflict with
> "[GIT PULL] Renesas ARM Based SoC Kconfig Cleanups for v3.18",
> tagged as renesas-kconfig-cleanups-for-v3.18, which you
> have previously pulled.

Pulled into next/soc as well. One detail I noticed for the first time is
that the setup-*.c file hides the machine descriptor inside of #ifdef
CONFIG_USE_OF, which makes no sense since the file is only compiled
when ARCH_MULTIPLATFORM is set, and that does 'select USE_OF'.
It would be better not to add that #ifdef for new files, and you
could perhaps remove the existing ones after the conversion to
multiplatform is complete.

Thanks,

	Arnd

  parent reply	other threads:[~2014-09-09 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  4:22 [GIT PULL] Third Round of Renesas ARM Based SoC Soc Updates for v3.18 Simon Horman
2014-09-09  4:22 ` [PATCH 1/2] ARM: shmobile: support Cortex-A7 in shmobile_init_delay() Simon Horman
2014-09-09  4:22 ` [PATCH 2/2] ARM: shmobile: Initial r8a7794 SoC support Simon Horman
2014-09-09 15:20 ` Arnd Bergmann [this message]
2014-09-09 23:52   ` [GIT PULL] Third Round of Renesas ARM Based SoC Soc Updates for v3.18 Simon Horman

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=4196537.hvL3OIMxQq@wuerfel \
    --to=arnd@arndb.de \
    --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