linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos: dts: cros5250: add EC device
Date: Sat, 27 Apr 2013 15:12:31 -0700	[thread overview]
Message-ID: <20130427221231.GA10453@quad.lixom.net> (raw)
In-Reply-To: <CAD=FV=VQg=2R_x11xuGiA0kNj1NXHUM3TUzVJC-F0ZWO39JRdw@mail.gmail.com>

On Fri, Apr 26, 2013 at 09:04:56PM -0700, Doug Anderson wrote:
> Olof,
> 
> On Fri, Apr 26, 2013 at 6:04 PM, Olof Johansson <olof@lixom.net> wrote:
> > Ah, yes, of course. As discussed off-mail, I was mislead by some contents in
> > our local tree. :)
> 
> Sorry about that--that was my fault.  Things have landed in a
> different order in one of our local trees.

Yeah, no worries.

> > Kukjin, I'd really like to pick up these patches for 3.10, since they're
> > isolated to just dts changes and gets keyboard working on the Chromebook. Can
> > you ack them and I'll just collect them this time?
> 
> I'm pretty sure that Kukjin is OK with them.  Kukjin responded earlier and said:
> 
> > I'm fine on 2nd and 3rd patches. Shall I take only two patches without 1st
> > one in samsung tree?
> 
> At the time we were waiting for Wolfram to get patch 1 into his tree,
> which is now done.
> 
> ...but waiting for his official Ack is good, too.  ;)


Ah, yes, sounds good. I'll apply these to a late/* branch on arm-soc. It's only
touching cros5250 and snow device trees anyway.

v2 of the patch posted as separate comment.


-Olof

  reply	other threads:[~2013-04-27 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 23:42 [PATCH] ARM: exynos: dts: cros5250: add EC device Olof Johansson
2013-04-26 23:56 ` Doug Anderson
2013-04-27  1:04   ` Olof Johansson
2013-04-27  4:04     ` Doug Anderson
2013-04-27 22:12       ` Olof Johansson [this message]
2013-04-28  6:33       ` Kukjin Kim
2013-04-27 22:14 ` [PATCH v2] " Olof Johansson
2013-04-27 22:31   ` Doug Anderson

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=20130427221231.GA10453@quad.lixom.net \
    --to=olof@lixom.net \
    --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).