public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: "Wolfgang Grandegger" <wg@grandegger.com>,
	"Wolfram Sang" <w.sang@pengutronix.de>,
	"Christian Pellegrin" <chripell@fsfe.org>,
	"Barry Song" <21cnbao@gmail.com>,
	"Samuel Ortiz" <sameo@linux.intel.com>,
	<socketcan-core@lists.berlios.de>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	<andrew.chih.howe.khor@intel.com>, <qi.wang@intel.com>,
	<margie.foster@intel.com>, <yong.y.wang@intel.com>,
	<kok.howg.ewe@intel.com>, <joel.clark@intel.com>
Subject: Re: [PATCH net-next-2.6 v6 06/20] can: EG20T PCH: Fix endianness issue
Date: Thu, 2 Dec 2010 13:47:10 +0900	[thread overview]
Message-ID: <00a201cb91db$fd36e650$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 001101cb90e8$e60c76a0$66f8800a@maildom.okisemi.com

Hi Marc,

Again, do you have any comments for v6 other patches ?
If you don't have, please give us your "Acked" for each patch.

==Current status of v6 series==
01/20: Acked
02/20:
03/20:
04/20:
05/20: Acked
06/20: I got your comments. Now modifying
07/20:
08/20:
09/20:
10/20:
11/20: Acked
12/20:
13/20: Acked
14/20:
15/20:
16/20:
17/20:
18/20:
19/20:
20/20:

Thanks,
-------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

  reply	other threads:[~2010-12-02  4:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  4:20 [PATCH net-next-2.6 v6 06/20] can: EG20T PCH: Fix endianness issue Tomoya MORINAGA
2010-11-30 12:05 ` Marc Kleine-Budde
2010-11-30 23:47   ` Tomoya MORINAGA
2010-12-02  4:47     ` Tomoya MORINAGA [this message]
2010-12-02 21:15 ` David Miller
2010-12-02 21:17   ` David Miller

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='00a201cb91db$fd36e650$66f8800a@maildom.okisemi.com' \
    --to=tomoya-linux@dsn.okisemi.com \
    --cc=21cnbao@gmail.com \
    --cc=andrew.chih.howe.khor@intel.com \
    --cc=chripell@fsfe.org \
    --cc=davem@davemloft.net \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margie.foster@intel.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=sameo@linux.intel.com \
    --cc=socketcan-core@lists.berlios.de \
    --cc=w.sang@pengutronix.de \
    --cc=wg@grandegger.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