From: Tony Lindgren <tony@atomide.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
green@linuxhacker.ru
Subject: Re: [PATCH 2/3] Add tps65921 chip
Date: Sun, 3 Jul 2011 23:52:38 -0700 [thread overview]
Message-ID: <20110704065238.GO23145@atomide.com> (raw)
In-Reply-To: <20110701113726.GJ12106@sortiz-mobl>
* Samuel Ortiz <sameo@linux.intel.com> [110701 04:32]:
> Hi Tony,
>
> On Fri, Jul 01, 2011 at 12:35:58AM -0700, Tony Lindgren wrote:
> > Samuel,
> >
> > * green@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@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.
OK thanks!
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] Add tps65921 chip
Date: Sun, 3 Jul 2011 23:52:38 -0700 [thread overview]
Message-ID: <20110704065238.GO23145@atomide.com> (raw)
In-Reply-To: <20110701113726.GJ12106@sortiz-mobl>
* Samuel Ortiz <sameo@linux.intel.com> [110701 04:32]:
> 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.
OK thanks!
Tony
next prev parent reply other threads:[~2011-07-04 6:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 15:45 Initial B&N Nook Color support, take six green
2011-06-14 15:45 ` [PATCH 1/3] Initial B&N Nook Color (encore) support green
2011-06-14 15:45 ` [PATCH 2/3] Add tps65921 chip green
2011-07-01 7:35 ` Tony Lindgren
2011-07-01 7:35 ` Tony Lindgren
2011-07-01 11:37 ` Samuel Ortiz
2011-07-01 11:37 ` Samuel Ortiz
2011-07-04 6:52 ` Tony Lindgren [this message]
2011-07-04 6:52 ` Tony Lindgren
2011-06-14 15:45 ` [PATCH 3/3] Update Nook Color machine 3284 to common Encore name green
2011-06-30 13:35 ` Tony Lindgren
2011-06-30 13:35 ` Tony Lindgren
2011-07-11 15:21 ` Russell King - ARM Linux
2011-07-11 15:21 ` Russell King - ARM Linux
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 6:05 Initial B&N Nook Color support, take five green
2011-06-06 6:05 ` [PATCH 2/3] Add tps65921 chip green
2011-05-22 21:04 Initial B&N Nook Color support, take four green
2011-05-22 21:04 ` [PATCH 2/3] Add tps65921 chip green
2011-05-22 21:04 ` 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=20110704065238.GO23145@atomide.com \
--to=tony@atomide.com \
--cc=green@linuxhacker.ru \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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.