From: Tony Lindgren <tony@atomide.com>
To: "Eugeny S. Mints" <eugeny.mints@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH] TWL4030: Reset header file to mainline
Date: Wed, 17 Jun 2009 07:23:59 -0700 [thread overview]
Message-ID: <20090617142358.GW6605@atomide.com> (raw)
In-Reply-To: <20090617141137.GJ6374@everest>
* Amit Kucheria <amit.kucheria@verdurent.com> [090617 07:19]:
> On 09 Jun 17, Eugeny S. Mints wrote:
> > 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?
>
> I think the idea is that (and Tony should correct me here if I'm wrong)
> core OMAP code is handled here while peripheral drivers will all go
> directly to their respective susbsystem maintainers upstream.
Yeah, so for the twl4030 patches that's mostly drivers/mfd.
If we pile up things to linux-omap, that code never goes anywhere
and keeps piling up!
And now for the first time ever, we have pretty much all we need
working in the mainline kernel! So that should be the stable base
for any distros or prodcuts starting with 2.6.31.
Tony
prev parent reply other threads:[~2009-06-17 14:23 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
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 [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=20090617142358.GW6605@atomide.com \
--to=tony@atomide.com \
--cc=eugeny.mints@gmail.com \
--cc=linux-omap@vger.kernel.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