Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Olof Johansson' <olof@lixom.net>
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,
	'Abhilash Kesavan' <a.kesavan@samsung.com>
Subject: RE: [GIT PULL 5/5] Samsung Exynos MCPM support for 3.16
Date: Fri, 30 May 2014 10:26:24 +0900	[thread overview]
Message-ID: <060801cf7ba6$2b815ec0$82841c40$@samsung.com> (raw)
In-Reply-To: <CAOesGMj=c3RVQs2=xtWV82nMxjD9w6QNv2Wz4wTi7KrOuHYTig@mail.gmail.com>

Olof Johansson wrote:
> 
> On Wed, May 21, 2014 at 10:38 PM, Olof Johansson <olof@lixom.net> wrote:
> > On Tue, May 20, 2014 at 10:11:54AM +0900, Kukjin Kim wrote:
> >> The following changes since commit d7067f1c5fa0232001502569c6878d22308da268:
> >>
> >>   devicetree: bindings: document SYSRAM binding (2014-05-15 03:30:29 +0900)
> >>
> >> are available in the git repository at:
> >>
> >>   http://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
> >> tags/exynos-mcpm
> >>
> >> for you to fetch changes up to ccf5511797cd4b48d20a85fa1778f5608eac9fd7:
> >>
> >>   ARM: EXYNOS: Add MCPM call-back functions (2014-05-16 04:26:30 +0900)
> >>
> >> ----------------------------------------------------------------
> >> Exynos MCPM support for v3.16
> >>
> >> - adding MCPM backend support for SMP secondary boot and core switching
> >> on Samsung's Exynos5420.
> >>
> >> Tested on exynos5420-smdk5420 and exynos5420 based chromebook (peach-pit)
> >> using the "/dev/b.L_switcher" user interface. Secondary core boot-up has
> >> also been tested on both the boards.
> >
> > This goes with new SoC enablement as well; we'll merge it after multi-platform.
> 
> Merged now, since multiplatform is going in as well.
> 
> What confused me for a while here was that this branch was based on a
> partial version of the DT branch, but it didn't match any of the

Yeah, I just thought that it would be better if this could be having minimally
the dependent patches.

> branch heads we had merged in. It's not wrong to do so but it's useful
> to get a heads up in the pull request.
> 
OK, I see. I will do as you suggested in future.

Thanks,
Kukjin

      reply	other threads:[~2014-05-30  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20  1:11 [GIT PULL 5/5] Samsung Exynos MCPM support for 3.16 Kukjin Kim
2014-05-22  5:38 ` Olof Johansson
2014-05-22 11:19   ` Kukjin Kim
2014-05-29 16:52   ` Olof Johansson
2014-05-30  1:26     ` Kukjin Kim [this message]

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='060801cf7ba6$2b815ec0$82841c40$@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=a.kesavan@samsung.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox