From: "Eugeny S. Mints" <eugeny.mints@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Amit Kucheria <amit.kucheria@verdurent.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] TWL4030: Reset header file to mainline
Date: Wed, 17 Jun 2009 18:20:24 +0400 [thread overview]
Message-ID: <4A38FBA8.8090406@gmail.com> (raw)
In-Reply-To: <20090617140648.GT6605@atomide.com>
Tony Lindgren wrote:
> * Eugeny S. Mints <eugeny.mints@gmail.com> [090617 06:46]:
>
>> Amit Kucheria wrote:
>>
>>> Reset twl4030.h to what is upstream. Patches to restore twl4030_power
>>> functionality will follow directly to lkml.
>>>
>>>
>>>
>> development against upstream is great. But what will be left for
>> this mail list if we send all patches directly to lkml?
>>
>
> Anything touching arch/arm/*omap*.
>
I'm not sure how many non-omap based boards out there are using twl4030
chip and if a separate mfd mail list exists.
But until any of the above is true I personally feel that twl4030
related discussions naturally fall into omap mail list.
> Also, while waiting things to get to mainline, we can merge in various
> topic branches, such as PM, DSS2. So basically linux-omap master branch
> will shortly be just a queue of things going to the mainline tree while
> waiting for the next merge window.
>
>
ok
> Regards,
>
> Tony
>
>
next prev parent reply other threads:[~2009-06-17 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 11:29 [PATCH] TWL4030: Reset header file to mainline Amit Kucheria
2009-06-17 11:42 ` Felipe Balbi
2009-06-17 11:44 ` Tony Lindgren
2009-06-17 13:45 ` Eugeny S. Mints
2009-06-17 14:06 ` Tony Lindgren
2009-06-17 14:20 ` Eugeny S. Mints [this message]
2009-06-17 14:56 ` Mark Brown
2009-06-18 12:50 ` Kalle Valo
2009-06-17 14:11 ` Amit Kucheria
2009-06-17 14:23 ` Tony Lindgren
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=4A38FBA8.8090406@gmail.com \
--to=eugeny.mints@gmail.com \
--cc=amit.kucheria@verdurent.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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