public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: "Thomas Gleixner" <tglx@linutronix.de>, <meego-dev@meego.com>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	<qi.wang@intel.com>, <yong.y.wang@intel.com>,
	<andrew.chih.howe.khor@intel.com>, <arjan@linux.intel.com>,
	<gregkh@suse.de>, "Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35
Date: Tue, 31 Aug 2010 15:57:05 +0900	[thread overview]
Message-ID: <004a01cb48d9$b9eed010$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: AANLkTimmOdiAdjxix_JQUG21bYRU2bKw7OD=0HJDWwLy@mail.gmail.com

----- Original Message ----- 
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>; <meego-dev@meego.com>; "LKML" <linux-kernel@vger.kernel.org>; "David
Brownell" <dbrownell@users.sourceforge.net>; <qi.wang@intel.com>; <yong.y.wang@intel.com>;
<andrew.chih.howe.khor@intel.com>; <arjan@linux.intel.com>; <gregkh@suse.de>; "Tomoya MORINAGA"
<morinaga526@dsn.okisemi.com>; "David Woodhouse" <dwmw2@infradead.org>; "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Sent: Tuesday, August 31, 2010 3:53 PM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35


> On Tue, Aug 31, 2010 at 12:47 AM, Masayuki Ohtake
> <masa-korg@dsn.okisemi.com> wrote:
> >> Regardless, the topcliff spi driver can still be merged into mainline
> >> without the spi_device registration code, and you can keep your
> >> personal copy of spi_pch_device.c for testing while the details about
> >> device tree support for x86 get worked out.
> >>
> >> g.
> >>
> > Hi Grant,
> >
> > Thank you very much.
> > I could understand well.
> >
> > Can I post our SPI patch for Topcliff without 'of_node' code and spi_device registration code?
>
> yes.
>
> g.
>

OK!

I will post our modified SPI patch soon.

Thanks, Ohtake(OKISemi)



  reply	other threads:[~2010-08-31  6:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C77BD91.9070302@dsn.okisemi.com>
2010-08-27 18:33 ` [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35 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 [this message]
2010-08-31 12:09   ` Masayuki Ohtake
2010-09-06 11:09 Masayuki Ohtak
2010-09-10  6:03 ` 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-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] <4C6131C2.4080101@dsn.okisemi.com>
2010-08-10 17:10 ` Greg KH
2010-08-11  1:25   ` Wang, Qi

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='004a01cb48d9$b9eed010$66f8800a@maildom.okisemi.com' \
    --to=masa-korg@dsn.okisemi.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=dwmw2@infradead.org \
    --cc=grant.likely@secretlab.ca \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meego-dev@meego.com \
    --cc=morinaga526@dsn.okisemi.com \
    --cc=qi.wang@intel.com \
    --cc=tglx@linutronix.de \
    --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