All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Kukjin Kim <kgene@kernel.org>, 'Olof Johansson' <olof@lixom.net>,
	Kevin Hilman <khilman@linaro.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	arm@kernel.org, Mike Turquette <mturquette@linaro.org>
Subject: Re: [GIT PULL 4/4] Samsung exynos7 updates for v3.19
Date: Fri, 28 Nov 2014 13:35:55 +0100	[thread overview]
Message-ID: <201411281335.55663.arnd@arndb.de> (raw)
In-Reply-To: <5476CD88.1030406@kernel.org>

On Thursday 27 November 2014, Kukjin Kim wrote:
> Samsung arch/arm64 DT updates for v3.19
> 
> - to support ARMv8 based exynos7 SoC
>   : add initial device tree and add pinctrl, PMU, mmc, i2c, rtc,
>     watchdog, and adc nodes for exynos7 SoC and exynos7 based
>     espresso board.
> 
> NOTE that this is including following dependencies
> : cleanup/dts-subdirs in arm-soc for arm64 vendor support
> : tags/samsung-driver for samsung serial
> : for-v3.19/exynos-clk in samsung-clk tree for exynos7 clk
> 
> One more NOTE, for support exynos7 we need Liviu's "arm64: Create
> link to include/dt-bindings to enable C preprocessor use" in arm-soc
> tree and arm64 defconfig update should be handled directly.

I'm confused by the dependencies. I don't see a "for-v3.19/exynos-clk"
in arm-soc, you haven't put the clk maintainer on Cc and I see no indication
that he has this in his tree already, so I'm not pulling this until further
clarification.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] Samsung exynos7 updates for v3.19
Date: Fri, 28 Nov 2014 13:35:55 +0100	[thread overview]
Message-ID: <201411281335.55663.arnd@arndb.de> (raw)
In-Reply-To: <5476CD88.1030406@kernel.org>

On Thursday 27 November 2014, Kukjin Kim wrote:
> Samsung arch/arm64 DT updates for v3.19
> 
> - to support ARMv8 based exynos7 SoC
>   : add initial device tree and add pinctrl, PMU, mmc, i2c, rtc,
>     watchdog, and adc nodes for exynos7 SoC and exynos7 based
>     espresso board.
> 
> NOTE that this is including following dependencies
> : cleanup/dts-subdirs in arm-soc for arm64 vendor support
> : tags/samsung-driver for samsung serial
> : for-v3.19/exynos-clk in samsung-clk tree for exynos7 clk
> 
> One more NOTE, for support exynos7 we need Liviu's "arm64: Create
> link to include/dt-bindings to enable C preprocessor use" in arm-soc
> tree and arm64 defconfig update should be handled directly.

I'm confused by the dependencies. I don't see a "for-v3.19/exynos-clk"
in arm-soc, you haven't put the clk maintainer on Cc and I see no indication
that he has this in his tree already, so I'm not pulling this until further
clarification.

	Arnd

  reply	other threads:[~2014-11-28 12:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  7:06 [GIT PULL 4/4] Samsung exynos7 updates for v3.19 Kukjin Kim
2014-11-27  7:06 ` Kukjin Kim
2014-11-28 12:35 ` Arnd Bergmann [this message]
2014-11-28 12:35   ` Arnd Bergmann
2014-11-29  0:13   ` Kukjin Kim
2014-11-29  0:13     ` Kukjin Kim
2014-12-03 10:49   ` Kukjin Kim
2014-12-03 10:49     ` Kukjin Kim

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=201411281335.55663.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=kgene@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=olof@lixom.net \
    /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.