public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
Cc: margie.foster@intel.com,
	"Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
	yong.y.wang@intel.com, joel.clark@intel.com,
	kok.howg.ewe@intel.com, andrew.chih.howe.khor@intel.com,
	qi.wang@intel.com, linux-kernel@vger.kernel.org,
	"Mike Frysinger" <vapier@gentoo.org>,
	"Richard R�jfors" <richard.rojfors@mocean-labs.com>,
	"Alek Du" <alek.du@intel.com>,
	"Randy Dunlap" <randy.dunlap@oracle.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	meego-dev@meego.com
Subject: Re: [MeeGo-Dev][PATCH v4] Topcliff: Update PCH_GPIO driver to 2.6.35
Date: Tue, 5 Oct 2010 20:56:17 -0700	[thread overview]
Message-ID: <20101006035616.GA30795@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <000601cb6501$524d2030$66f8800a@maildom.okisemi.com>

On Wed, Oct 06, 2010 at 11:50:58AM +0900, Masayuki Ohtake wrote:

> BTW, for adding to Linus's kernel tree, Do we need another action ? or
> Do we only just wait ?

The gpio tree is pretty much orphaned at the minute, I'd guess Andrew
Morton (who's already CCed) would be the most likely person to pick this
up since it's not a MFD device.

      parent reply	other threads:[~2010-10-06  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06  0:17 [MeeGo-Dev][PATCH v4] Topcliff: Update PCH_GPIO driver to 2.6.35 Masayuki Ohtak
2010-10-06  0:38 ` Mark Brown
     [not found]   ` <000601cb6501$524d2030$66f8800a@maildom.okisemi.com>
2010-10-06  3:56     ` Mark Brown [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=20101006035616.GA30795@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alek.du@intel.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margie.foster@intel.com \
    --cc=masa-korg@dsn.okisemi.com \
    --cc=meego-dev@meego.com \
    --cc=morinaga526@dsn.okisemi.com \
    --cc=qi.wang@intel.com \
    --cc=randy.dunlap@oracle.com \
    --cc=richard.rojfors@mocean-labs.com \
    --cc=sameo@linux.intel.com \
    --cc=vapier@gentoo.org \
    --cc=yong.y.wang@intel.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