public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] Add tps65921 chip
Date: Fri, 1 Jul 2011 13:37:26 +0200	[thread overview]
Message-ID: <20110701113726.GJ12106@sortiz-mobl> (raw)
In-Reply-To: <20110701073557.GF23145@atomide.com>

Hi Tony,

On Fri, Jul 01, 2011 at 12:35:58AM -0700, Tony Lindgren wrote:
> Samuel,
> 
> * green at linuxhacker.ru <green@linuxhacker.ru> [110614 08:42]:
> > From: Oleg Drokin <green@linuxhacker.ru>
> > 
> > Very similar to TPS65920
> > List of differences: http://www.ti.com/litv/pdf/swcu066b
> > 
> > CC: sameo at linux.intel.com
> > Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
> 
> Looks like this one can be merged independently of the rest of the
> Nook patches via your mfd tree. Care to queue this?
I asked Oleg to rebase this patch against my for-next branch as it was not
applying cleanly. But I never got the fixed patch.
I fixed it up now, and it's applied.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

  reply	other threads:[~2011-07-01 11:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1308066307-415-1-git-send-email-green@linuxhacker.ru>
     [not found] ` <1308066307-415-4-git-send-email-green@linuxhacker.ru>
2011-06-30 13:35   ` [PATCH 3/3] Update Nook Color machine 3284 to common Encore name Tony Lindgren
2011-07-11 15:21     ` Russell King - ARM Linux
     [not found] ` <1308066307-415-3-git-send-email-green@linuxhacker.ru>
2011-07-01  7:35   ` [PATCH 2/3] Add tps65921 chip Tony Lindgren
2011-07-01 11:37     ` Samuel Ortiz [this message]
2011-07-04  6:52       ` Tony Lindgren
2011-05-22 21:04 Initial B&N Nook Color support, take four green at linuxhacker.ru
2011-05-22 21:04 ` [PATCH 2/3] Add tps65921 chip green at linuxhacker.ru

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=20110701113726.GJ12106@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --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