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
prev parent reply other threads:[~2015-08-13 10:13 UTC|newest]
Thread overview: 3+ 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 9:21 ` Olof Johansson
2015-08-13 10:13 ` 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='007a01d0d5b0$c53d6580$4fb83080$@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).