All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	'Viresh Kumar' <viresh.kumar@linaro.org>,
	'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
	'Michael Turquette' <mturquette@baylibre.com>,
	'Mike Turquette' <mturquette@linaro.org>
Subject: RE: [GIT PULL 2nd 3/4] Samsung driver 2nd updates for v4.3
Date: Thu, 13 Aug 2015 19:13:59 +0900	[thread overview]
Message-ID: <007a01d0d5b0$c53d6580$4fb83080$@kernel.org> (raw)
In-Reply-To: <20150813092144.GD30160@localhost>

Olof Johansson wrote:
> 
> On Thu, Aug 13, 2015 at 09:12:59AM +0900, Kukjin Kim wrote:
> > Hi,
> >
> > I've created the signed tag based on previous tags/samsung-driver so you
> > can see several merge in there. To support cpufreq-dt driver requires
> > clk/cpufreq/exynos changes together and clk/cpufreq maintainers are
> > aware of this changes. And we can remove exynos cpufreq driver at last.
> >
> > Note this drivers update is including previous dependencies and if
> > you're OK, please pull.
> 
> Again, this needs to be revisited.
> 
YES.

> Please try to keep the dependency only driver->dt if you can,
> and we can merge drivers before DT this release cycle. If you do
> driver->dt->driver->dt like here then things get messy.
> 
It looks better. OK.

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 2nd 3/4] Samsung driver 2nd updates for v4.3
Date: Thu, 13 Aug 2015 19:13:59 +0900	[thread overview]
Message-ID: <007a01d0d5b0$c53d6580$4fb83080$@kernel.org> (raw)
In-Reply-To: <20150813092144.GD30160@localhost>

Olof Johansson wrote:
> 
> On Thu, Aug 13, 2015 at 09:12:59AM +0900, Kukjin Kim wrote:
> > Hi,
> >
> > I've created the signed tag based on previous tags/samsung-driver so you
> > can see several merge in there. To support cpufreq-dt driver requires
> > clk/cpufreq/exynos changes together and clk/cpufreq maintainers are
> > aware of this changes. And we can remove exynos cpufreq driver at last.
> >
> > Note this drivers update is including previous dependencies and if
> > you're OK, please pull.
> 
> Again, this needs to be revisited.
> 
YES.

> Please try to keep the dependency only driver->dt if you can,
> and we can merge drivers before DT this release cycle. If you do
> driver->dt->driver->dt like here then things get messy.
> 
It looks better. OK.

Thanks,
Kukjin

  reply	other threads:[~2015-08-13 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  0:12 [GIT PULL 2nd 3/4] Samsung driver 2nd updates for v4.3 Kukjin Kim
2015-08-13  0:12 ` Kukjin Kim
2015-08-13  9:21 ` Olof Johansson
2015-08-13  9:21   ` Olof Johansson
2015-08-13 10:13   ` Kukjin Kim [this message]
2015-08-13 10:13     ` 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='007a01d0d5b0$c53d6580$4fb83080$@kernel.org' \
    --to=kgene@kernel.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=mturquette@linaro.org \
    --cc=olof@lixom.net \
    --cc=viresh.kumar@linaro.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 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.