linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] Samsung exynos7 updates for v3.19
Date: Sat, 29 Nov 2014 09:13:02 +0900	[thread overview]
Message-ID: <013701d00b69$3d7761d0$b8662570$@kernel.org> (raw)
In-Reply-To: <201411281335.55663.arnd@arndb.de>

Arnd Bergmann wrote:
> 
> 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.
> 
Hi,

Sorry for insufficient description.

Since the exynos7 stuff requires regarding clk stuff for kernel build, I talked
to Mike, Sylwester and Mike suggested pulling the branch into Samsung tree.

http://www.spinics.net/lists/linux-samsung-soc/msg39368.html

If any problems, please let me know.

Thanks,
Kukjin

  reply	other threads:[~2014-11-29  0:13 UTC|newest]

Thread overview: 4+ 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-28 12:35 ` Arnd Bergmann
2014-11-29  0:13   ` Kukjin Kim [this message]
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='013701d00b69$3d7761d0$b8662570$@kernel.org' \
    --to=kgene@kernel.org \
    --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).