From: Tony Lindgren <tony@atomide.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Lesly A M <leslyam@ti.com>,
linux-omap@vger.kernel.org, Lesly A M <x0080970@ti.com>,
Nishanth Menon <nm@ti.com>, David Derrick <dderrick@ti.com>,
Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Subject: Re: [PATCH] [PATCH v4 1/5] omap3: pm: fix for twl4030 script load
Date: Wed, 7 Apr 2010 06:42:11 -0700 [thread overview]
Message-ID: <20100407134211.GJ7153@atomide.com> (raw)
In-Reply-To: <20100402102240.GE8010@sortiz.org>
* Samuel Ortiz <sameo@linux.intel.com> [100402 03:18]:
<snip>
> Tony, I think it would make sense for this patchset to go through the
> linux-omap tree.
> If you agree, please add my:
> Acked-by: Samuel Ortiz <sameo@linux.intel.com>
>
> to the patch below.
I'm pretty much overwhelmed already with all the patches already,
so I'd rather stay out of the drivers/* path for now thanks.
How about if somebody familiar with the twl hardware and driver
sets up the drivers/mfd/twl* patches to some git tree? Then we
keep merging that into linux-omap master branch for testing. And
then Samuel pulls it as needed and sends them to Linus.
Maybe Peter p2 De Schrijver could do it? Peter knows a lot about
this driver and hardware, deals with it on regular basis, and
wrote a lot of the code that Amit later got merged upstream.
Comments?
Regards,
Tony
prev parent reply other threads:[~2010-04-07 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 10:20 [PATCH] [PATCH v4 1/5] omap3: pm: fix for twl4030 script load Lesly A M
2010-04-02 10:22 ` Samuel Ortiz
2010-04-07 13:42 ` Tony Lindgren [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=20100407134211.GJ7153@atomide.com \
--to=tony@atomide.com \
--cc=dderrick@ti.com \
--cc=leslyam@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.de-schrijver@nokia.com \
--cc=sameo@linux.intel.com \
--cc=x0080970@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox