public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Eugeny S. Mints" <eugeny.mints@gmail.com>
Cc: 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: Wed, 17 Jun 2009 15:56:53 +0100	[thread overview]
Message-ID: <20090617145652.GC10550@sirena.org.uk> (raw)
In-Reply-To: <4A38FBA8.8090406@gmail.com>

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.

  reply	other threads:[~2009-06-17 14:56 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 [this message]
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=20090617145652.GC10550@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=amit.kucheria@verdurent.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox