From: Arnd Bergmann <arnd@arndb.de>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Olof Johansson' <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Chander Kashyap <chander.kashyap@linaro.org>
Subject: Re: [GIT PULL 08/10] Samsung SoC EXYNOS5420 for v3.11
Date: Thu, 20 Jun 2013 22:58:26 +0200 [thread overview]
Message-ID: <201306202258.26968.arnd@arndb.de> (raw)
In-Reply-To: <51C0BC74.1060502@samsung.com>
On Tuesday 18 June 2013, Kukjin Kim wrote:
> ----------------------------------------------------------------
> based on tags/common-clk-audio
> - add support for exynos5420 SoC
>
> ----------------------------------------------------------------
This is causing me a little pain because of the deep dependency
chain. I'll probably have to create a next/soc2 branch, but
will first try to merge the Renesas pull requests, which may have
similar problems.
If it's possible to rebase this one not to have any dependencies
other than the branches merged into next/cleanup and next/soc,
I can pull it more easily, as long as I can figure out how
to merge it with the common-clk-audio branch.
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 08/10] Samsung SoC EXYNOS5420 for v3.11
Date: Thu, 20 Jun 2013 22:58:26 +0200 [thread overview]
Message-ID: <201306202258.26968.arnd@arndb.de> (raw)
In-Reply-To: <51C0BC74.1060502@samsung.com>
On Tuesday 18 June 2013, Kukjin Kim wrote:
> ----------------------------------------------------------------
> based on tags/common-clk-audio
> - add support for exynos5420 SoC
>
> ----------------------------------------------------------------
This is causing me a little pain because of the deep dependency
chain. I'll probably have to create a next/soc2 branch, but
will first try to merge the Renesas pull requests, which may have
similar problems.
If it's possible to rebase this one not to have any dependencies
other than the branches merged into next/cleanup and next/soc,
I can pull it more easily, as long as I can figure out how
to merge it with the common-clk-audio branch.
Arnd
next prev parent reply other threads:[~2013-06-20 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 20:00 [GIT PULL 08/10] Samsung SoC EXYNOS5420 for v3.11 Kukjin Kim
2013-06-18 20:00 ` Kukjin Kim
2013-06-20 20:58 ` Arnd Bergmann [this message]
2013-06-20 20:58 ` Arnd Bergmann
2013-06-20 22:58 ` Kukjin Kim
2013-06-20 22:58 ` Kukjin Kim
2013-06-21 7:36 ` Arnd Bergmann
2013-06-21 7:36 ` Arnd Bergmann
2013-06-21 13:03 ` Arnd Bergmann
2013-06-21 13:03 ` Arnd Bergmann
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=201306202258.26968.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=chander.kashyap@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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.