public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Masayuki Ohtak <masa-korg@dsn.okisemi.com>
Cc: meego-dev@meego.com, LKML <linux-kernel@vger.kernel.org>,
	Wang Qi <qi.wang@intel.com>, Wang Yong Y <yong.y.wang@intel.com>,
	Andrew <andrew.chih.howe.khor@intel.com>,
	arjan@linux.intel.com
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35
Date: Tue, 10 Aug 2010 10:10:42 -0700	[thread overview]
Message-ID: <20100810171042.GD21220@suse.de> (raw)
In-Reply-To: <4C6131C2.4080101@dsn.okisemi.com>

On Tue, Aug 10, 2010 at 08:02:26PM +0900, Masayuki Ohtak wrote:
> SPI driver of Topcliff PCH
> 
> Topcliff PCH is the platform controller hub that is going to be used in
> Intel's upcoming general embedded platform. All IO peripherals in
> Topcliff PCH are actually devices sitting on AMBA bus. 
> Topcliff PCH has SPI I/F. Using this I/F, it is able to access system
> devices connected to SPI.
> 
> Signed-off-by: Masayuki Ohtake <masa-korg@dsn.okisemi.com>
> ---
>  drivers/spi/Kconfig                    |   26 +
>  drivers/spi/Makefile                   |    4 +
>  drivers/spi/pch_spi.h                  |  177 +++
>  drivers/spi/pch_spi_main.c             | 1823 ++++++++++++++++++++++++++++++++
>  drivers/spi/pch_spi_platform_devices.c |   56 +

Any reason why you didn't run this by the Linux kernel SPI maintainers
and developers?  Please use the scripts/get_maintainer.pl script to find
the proper people if you don't want to look in the MAINTAINERS file to
find them that way.

thanks,

greg k-h

       reply	other threads:[~2010-08-10 17:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C6131C2.4080101@dsn.okisemi.com>
2010-08-10 17:10 ` Greg KH [this message]
2010-08-11  1:25   ` [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35 Wang, Qi
     [not found] <4C77BD91.9070302@dsn.okisemi.com>
2010-08-27 18:33 ` Grant Likely
2010-08-27 18:53   ` Thomas Gleixner
2010-08-27 18:54     ` Arjan van de Ven
2010-08-27 19:06       ` Thomas Gleixner
2010-08-27 19:20     ` Grant Likely
2010-08-30  7:28       ` Masayuki Ohtake
2010-08-30 12:44         ` Thomas Gleixner
2010-08-31  1:05           ` Masayuki Ohtake
2010-08-31  5:51             ` Grant Likely
2010-08-31  6:24               ` Masayuki Ohtake
2010-08-30 18:23         ` Grant Likely
2010-08-31  1:45           ` Masayuki Ohtake
2010-08-31  6:03             ` Grant Likely
2010-08-31  6:47               ` Masayuki Ohtake
2010-08-31  6:53                 ` Grant Likely
2010-08-31  6:57                   ` Masayuki Ohtake
2010-08-31 12:09   ` Masayuki Ohtake
2010-09-03  5:50 Masayuki Ohtake
2010-09-09 20:58 ` Linus Walleij
2010-09-10  0:27   ` Masayuki Ohtake
2010-09-10  1:30     ` Joe Perches
2010-09-10  1:41       ` Grant Likely
2010-09-10  2:05     ` Grant Likely
2010-09-10  4:55   ` Grant Likely
2010-09-14  2:52     ` Tomoya MORINAGA
2010-09-14  2:56       ` Grant Likely
     [not found] <4C80E2D5.1020104@dsn.okisemi.com>
2010-09-03 14:46 ` Grant Likely
2010-09-03 17:50   ` Linus Walleij
2010-09-03 17:57     ` Grant Likely
2010-09-06  6:19   ` Masayuki Ohtake
2010-09-08 19:40     ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
2010-09-06 11:09 Masayuki Ohtak
2010-09-10  6:03 ` Grant Likely

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=20100810171042.GD21220@suse.de \
    --to=gregkh@suse.de \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masa-korg@dsn.okisemi.com \
    --cc=meego-dev@meego.com \
    --cc=qi.wang@intel.com \
    --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