From: "Masayuki Ohtake" <masa-korg@dsn.okisemi.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
<margie.foster@intel.com>, <alan@linux.intel.com>,
<arjan@linux.intel.com>, <andrew.chih.howe.khor@intel.com>,
<qi.wang@intel.com>, <yong.y.wang@intel.com>,
"LKML" <linux-kernel@vger.kernel.org>, <meego-dev@meego.com>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35
Date: Thu, 2 Sep 2010 08:58:30 +0900 [thread overview]
Message-ID: <002401cb4a31$95116830$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 20100901230901.GA21326@suse.de
Hi Greg,
Thank you for your checking.
> Do you want me to queue it up for the .37 kernel merge
> through my tree, or through someone elses?
I want you to queue our phub patch through your tree.
Thanks, Ohtake(OKISemi)
----- Original Message -----
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>; <yong.y.wang@intel.com>; <qi.wang@intel.com>;
<andrew.chih.howe.khor@intel.com>; <arjan@linux.intel.com>; <alan@linux.intel.com>; <margie.foster@intel.com>; "Tomoya
MORINAGA" <morinaga526@dsn.okisemi.com>
Sent: Thursday, September 02, 2010 8:09 AM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35
> On Wed, Sep 01, 2010 at 09:16:30PM +0900, Masayuki Ohtak wrote:
> > Hi Greg,
> >
> > Sorry, we have modified again, for a bug(illegal return code) and
> > WARNING for building with the latest kernel.
> >
> > Please check below.
>
> Looks good. Do you want me to queue it up for the .37 kernel merge
> through my tree, or through someone elses?
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2010-09-01 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 12:16 [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35 Masayuki Ohtak
2010-09-01 23:09 ` Greg KH
2010-09-01 23:58 ` Masayuki Ohtake [this message]
2010-09-02 0:59 ` Greg KH
2010-09-02 1:02 ` Greg KH
2010-09-02 2:36 ` Masayuki Ohtake
2010-09-02 3:22 ` Greg KH
2010-09-02 3:29 ` Wang, Qi
2010-09-02 6:44 ` Masayuki Ohtake
2010-09-02 13:19 ` Greg KH
2010-09-03 0:22 ` Masayuki Ohtake
2010-09-03 2:14 ` Greg KH
2010-09-03 1:13 ` Wang, Qi
2010-09-02 6:38 ` Masayuki Ohtake
2010-09-02 13:18 ` Greg KH
2010-09-03 0:17 ` Masayuki Ohtake
2010-09-02 1:15 ` patch "add Packet hub driver for Topcliff Platform controller hub" added to gregkh-2.6 tree gregkh
-- strict thread matches above, loose matches on Subject: below --
2010-08-25 12:05 [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35 Masayuki Ohtak
2010-08-25 10:16 Masayuki Ohtak
2010-08-24 6:47 Masayuki Ohtak
2010-08-24 13:22 ` Greg KH
2010-08-18 9:10 Masayuki Ohtak
2010-08-18 13:14 ` Greg KH
2010-08-19 6:27 ` Masayuki Ohtake
2010-08-19 15:17 ` Greg KH
2010-08-20 6:53 ` Masayuki Ohtake
2010-08-19 12:25 ` Masayuki Ohtake
2010-08-19 15:22 ` Greg KH
2010-08-23 12:30 ` Masayuki Ohtake
2010-08-23 15:34 ` Greg KH
2010-08-24 0:02 ` Masayuki Ohtake
2010-08-24 6:46 ` Masayuki Ohtake
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='002401cb4a31$95116830$66f8800a@maildom.okisemi.com' \
--to=masa-korg@dsn.okisemi.com \
--cc=alan@linux.intel.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=arjan@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=margie.foster@intel.com \
--cc=meego-dev@meego.com \
--cc=morinaga526@dsn.okisemi.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 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.