linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Samsung fixes-2 for v4.0
Date: Fri, 06 Mar 2015 19:16:53 +0900	[thread overview]
Message-ID: <02cd01d057f6$ab1a8e40$014faac0$@kernel.org> (raw)
In-Reply-To: <2064108.qlOP0oDx90@wuerfel>

Arnd Bergmann wrote:
> 
+ Eduardo

Hi Arnd,

> On Tuesday 03 March 2015 04:00:14 Kukjin Kim wrote:
> > Please pull Samsung tmu and hdmi regression fixes for v4.0 and I know
> > this is quite big for fixes but I couldn't handle this series for
> > previous merge window because of dependency with driver side...sorry for
> > that and please pull so that we could support them in v4.0 on exynos
> > platforms.
> 
> What kind of dependency do you have there? It really should not be
> necessary to wait for driver changes, unless you do an incompatible
> DT binding change, which you should avoid.
> 
For TMU patches, I've asked Eduardo to provide topic branch for
'include/dt-bindings/thermal/thermal_exynos.h' has been added via thermal tree
because if I can't apply the patch in Samsung tree for arm-soc, kernel build
breakage will be happened. But I couldn't get Eduardo's topic branch.

http://www.spinics.net/lists/linux-samsung-soc/msg41877.html


For HDMI patches, I thought the DT changes have a dependency with "drm/exynos:
add support for 'hdmi' clock" so waited for its applying then in drm tree. But
I couldn't send it to arm-soc after that...

http://www.spinics.net/lists/linux-samsung-soc/msg42173.html


I asked about the situation (late DT changes?) when I sent a pull-request, then
I couldn't get a access my kernel.org because of biz. trip to China :(

http://www.spinics.net/lists/linux-samsung-soc/msg42235.html


> I've pulled it into fixes, but won't forward it until I hear a
> good explanation.
> 
As you know, basically I tried to make a clear branch for pull-request but in
that case, I couldn't find a solution. Sorry for the inconvenience.

I hope v4.0 can support them properly.

Thanks,
Kukjin

  parent reply	other threads:[~2015-03-06 10:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 19:00 [GIT PULL 2/2] Samsung fixes-2 for v4.0 Kukjin Kim
2015-03-04 20:04 ` Arnd Bergmann
2015-03-04 23:04   ` Arnd Bergmann
2015-03-05  0:38     ` Javier Martinez Canillas
2015-03-06  9:43       ` Kukjin Kim
2015-03-06 10:07         ` Javier Martinez Canillas
2015-03-14 13:17         ` Javier Martinez Canillas
2015-03-06 10:16   ` Kukjin Kim [this message]
2015-03-05 12:34     ` Eduardo Valentin
2015-03-09  7:44       ` Lukasz Majewski
2015-03-09  8:19         ` Kukjin Kim
2015-03-09  8:28           ` Lukasz Majewski
2015-03-12 11:15       ` 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='02cd01d057f6$ab1a8e40$014faac0$@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).