From: Kalle Valo <kalle.valo@iki.fi>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Eugeny S. Mints" <eugeny.mints@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Amit Kucheria <amit.kucheria@verdurent.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] TWL4030: Reset header file to mainline
Date: Thu, 18 Jun 2009 15:50:36 +0300 [thread overview]
Message-ID: <87tz2d7lk3.fsf@litku.valot.fi> (raw)
In-Reply-To: <20090617145652.GC10550@sirena.org.uk> (Mark Brown's message of "Wed\, 17 Jun 2009 15\:56\:53 +0100")
Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
> On Wed, Jun 17, 2009 at 06:20:24PM +0400, Eugeny S. Mints wrote:
>> Tony Lindgren wrote:
>
>>> 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.
>
> While the overwhelming majority of TWL4030 specifics will only actually
> be seen on OMAP systems (so CCing the OMAP list makes sense) the code
> also exists in the context of the rest of the kernel. It needs review
> by subsystem maintainers and people working on non-OMAP systems may have
> useful input based on their general experience of working on simiar
> parts - in general Linux terms the fact that you've got, for example, a
> keyboard controller is at least as relevant as the fact that it's likely
> to be used on an OMAP system.
>
> Many subsystems don't have a separate list and just use linux-kernel.
Yes, and nobody will blame if you CCed linux-omap list twl4030, quite
the opposite. Even if all omap code is in mainline, it doesn't mean that
this list will fade away. I would anticipate even the opposite, more
people might get interested.
--
Kalle Valo
next prev parent reply other threads:[~2009-06-18 12:50 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 [this message]
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=87tz2d7lk3.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=amit.kucheria@verdurent.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eugeny.mints@gmail.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 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.