From: Kukjin Kim <kgene@kernel.org>
To: 'Olof Johansson' <olof@lixom.net>, 'Kukjin Kim' <kgene@kernel.org>
Cc: arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
'Kevin Hilman' <khilman@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
'Krzysztof Kozlowski' <k.kozlowski@samsung.com>
Subject: RE: [GIT PULL 4/5] Samsung 2nd DT updates for v4.3
Date: Thu, 13 Aug 2015 19:02:57 +0900 [thread overview]
Message-ID: <004101d0d5af$3c688420$b5398c60$@kernel.org> (raw)
In-Reply-To: <20150813091814.GA30160@localhost>
Olof Johansson wrote:
>
> On Tue, Aug 04, 2015 at 04:29:25PM +0900, Kukjin Kim wrote:
> > Hi Arnd, Olof, Kevin
> >
> > This 2nd DT update branch is based tags/samsung-dt-1 +
> > v4.3-topic/clk-samsung branch because of dependency to support generic
> > cpufreq driver. Please pull.
> >
> > Thanks,
> > Kukjin
> >
> >
> > The following changes since commit e4a39d904c3c3e4855287b7325306289ff044b06:
> >
> > Merge branch 'v4.3-topic/clk-samsung' into v4.3-next/dt-samsung-2
> > (2015-07-24 12:54:00 +0900)
> >
> > are available in the git repository at:
> >
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/samsung-dt-2
>
> "clk: exynos5250: add cpu clock configuration data and instantiate cpu
> clock" is applied twice, once to your own branch, and once merged in
> from Mike's branch. That doesn't look right.
>
Oops, it's my fault. Sorry for that.
> Can you please respin? Thanks.
>
Sure, I'll tonight in my time.
Thanks,
Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Samsung 2nd DT updates for v4.3
Date: Thu, 13 Aug 2015 19:02:57 +0900 [thread overview]
Message-ID: <004101d0d5af$3c688420$b5398c60$@kernel.org> (raw)
In-Reply-To: <20150813091814.GA30160@localhost>
Olof Johansson wrote:
>
> On Tue, Aug 04, 2015 at 04:29:25PM +0900, Kukjin Kim wrote:
> > Hi Arnd, Olof, Kevin
> >
> > This 2nd DT update branch is based tags/samsung-dt-1 +
> > v4.3-topic/clk-samsung branch because of dependency to support generic
> > cpufreq driver. Please pull.
> >
> > Thanks,
> > Kukjin
> >
> >
> > The following changes since commit e4a39d904c3c3e4855287b7325306289ff044b06:
> >
> > Merge branch 'v4.3-topic/clk-samsung' into v4.3-next/dt-samsung-2
> > (2015-07-24 12:54:00 +0900)
> >
> > are available in the git repository at:
> >
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> > tags/samsung-dt-2
>
> "clk: exynos5250: add cpu clock configuration data and instantiate cpu
> clock" is applied twice, once to your own branch, and once merged in
> from Mike's branch. That doesn't look right.
>
Oops, it's my fault. Sorry for that.
> Can you please respin? Thanks.
>
Sure, I'll tonight in my time.
Thanks,
Kukjin
next prev parent reply other threads:[~2015-08-13 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 7:29 [GIT PULL 4/5] Samsung 2nd DT updates for v4.3 Kukjin Kim
2015-08-04 7:29 ` Kukjin Kim
2015-08-13 9:18 ` Olof Johansson
2015-08-13 9:18 ` Olof Johansson
2015-08-13 10:02 ` Kukjin Kim [this message]
2015-08-13 10:02 ` 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='004101d0d5af$3c688420$b5398c60$@kernel.org' \
--to=kgene@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=k.kozlowski@samsung.com \
--cc=khilman@linaro.org \
--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.