All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: "Samuel Ortiz" <sameo@linux.intel.com>,
	"Wolfram Sang" <w.sang@pengutronix.de>,
	"Ralf Baechle" <ralf@linux-mips.org>, <linux-i2c@vger.kernel.org>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"Ben Dooks \(embedded platforms\)" <ben-linux@fluff.org>,
	"Linus Walleij" <linus.walleij@stericsson.com>,
	"srinidhi kasagar" <srinidhi.kasagar@stericsson.com>,
	"Tomoya MORINAGA" <morinaga526@dsn.okisemi.com>,
	"Wang Qi\"" <qi.wang@intel.com>,
	"Wang Yong Y\"" <yong.y.wang@intel.com>, <kok.howg.ewe@intel.com>,
	<joel.clark@intel.com>, <andrew.chih.howe.khor@intel.com>
Subject: Re: [PATCH v3] Topcliff: Update PCH_I2C driver to 2.6.36
Date: Tue, 26 Oct 2010 18:47:37 +0900	[thread overview]
Message-ID: <001c01cb74f2$d3dd8990$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 20101026111322.738b0b14@endymion.delvare

Hi Jean,

On Tuesday, October 26, 2010 6:13 PM, Jean Delvare wrote:
> The _pch becomes redundant then, i2c-topcliff.c would be enough, but
> both are fine with me, as my initial concern is gone.
I agree.
I will modify to "i2c-topcliff.c".

> There's no Reviewed-by, Acked-by or Signed-off-by from anyone at Intel
> in the patch you posted. 
Must we get Intel's signature ? 
We have already got the following. Isn't  this enough ?
> Reviewed-by: Linus Walleij <linus.walleij@stericsson.com>

Though I haven't heard like the requirement,
if Intel's signature is mandatory, I will request to Intel.

Thanks, Tomoya(OKI SEMICONDUCTOR CO., LTD.)

WARNING: multiple messages have this Message-ID (diff)
From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	Wolfram Sang <w.sang@pengutronix.de>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-i2c@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
	Linus Walleij <linus.walleij@stericsson.com>,
	srinidhi kasagar <srinidhi.kasagar@stericsson.com>,
	Tomoya MORINAGA <morinaga526@dsn.okisemi.com>,
	"Wang Qi\"" <qi.wang@intel.com>,
	"Wang Yong Y\"" <yong.y.wang@intel.com>,
	kok.howg.ewe@intel.com, joel.clark@intel.com,
	andrew.chih.howe.khor@intel.com
Subject: Re: [PATCH v3] Topcliff: Update PCH_I2C driver to 2.6.36
Date: Tue, 26 Oct 2010 18:47:37 +0900	[thread overview]
Message-ID: <001c01cb74f2$d3dd8990$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 20101026111322.738b0b14@endymion.delvare

Hi Jean,

On Tuesday, October 26, 2010 6:13 PM, Jean Delvare wrote:
> The _pch becomes redundant then, i2c-topcliff.c would be enough, but
> both are fine with me, as my initial concern is gone.
I agree.
I will modify to "i2c-topcliff.c".

> There's no Reviewed-by, Acked-by or Signed-off-by from anyone at Intel
> in the patch you posted. 
Must we get Intel's signature ? 
We have already got the following. Isn't  this enough ?
> Reviewed-by: Linus Walleij <linus.walleij@stericsson.com>

Though I haven't heard like the requirement,
if Intel's signature is mandatory, I will request to Intel.

Thanks, Tomoya(OKI SEMICONDUCTOR CO., LTD.)

  reply	other threads:[~2010-10-26  9:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  3:06 [PATCH v3] Topcliff: Update PCH_I2C driver to 2.6.36 Tomoya
2010-10-26  3:06 ` Tomoya
2010-10-26  8:20 ` Jean Delvare
2010-10-26  8:20   ` Jean Delvare
2010-10-26  9:05   ` Tomoya MORINAGA
2010-10-26  9:05     ` Tomoya MORINAGA
2010-10-26  9:13     ` Jean Delvare
2010-10-26  9:13       ` Jean Delvare
2010-10-26  9:47       ` Tomoya MORINAGA [this message]
2010-10-26  9:47         ` Tomoya MORINAGA
2010-10-26 11:26         ` Jean Delvare
2010-10-26 11:26           ` Jean Delvare
2010-10-26 23:57           ` Tomoya MORINAGA
2010-10-26 23:57             ` Tomoya MORINAGA
2010-10-27 13:15           ` Linus Walleij
2010-10-27 13:15             ` Linus Walleij

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='001c01cb74f2$d3dd8990$66f8800a@maildom.okisemi.com' \
    --to=tomoya-linux@dsn.okisemi.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=ben-linux@fluff.org \
    --cc=joel.clark@intel.com \
    --cc=khali@linux-fr.org \
    --cc=kok.howg.ewe@intel.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morinaga526@dsn.okisemi.com \
    --cc=qi.wang@intel.com \
    --cc=ralf@linux-mips.org \
    --cc=sameo@linux.intel.com \
    --cc=srinidhi.kasagar@stericsson.com \
    --cc=w.sang@pengutronix.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 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.