From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "Marc Kleine-Budde" <mkl@pengutronix.de>
Cc: <andrew.chih.howe.khor@intel.com>,
"Samuel Ortiz" <sameo@linux.intel.com>, <margie.foster@intel.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<socketcan-core@lists.berlios.de>, <yong.y.wang@intel.com>,
<kok.howg.ewe@intel.com>,
"Wolfgang Grandegger" <wg@grandegger.com>, <joel.clark@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Christian Pellegrin" <chripell@fsfe.org>, <qi.wang@intel.com>
Subject: Re: [PATCH net-next-2.6 01/19 v5] can: EG20T PCH: Separate Interface Register(IF1/IF2)
Date: Mon, 29 Nov 2010 10:59:31 +0900 [thread overview]
Message-ID: <002201cb8f69$11d30050$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 4CEF864B.6080207@pengutronix.de
On Friday, November 26, 2010 7:04 PM, Marc Kleine-Budde wrote:
>> nitpick: it's unusual to have leading whitespace in the patch description.
> maybe it's a problem of your mailer.
I can see the whitespace created patch by "git format-patch"
I show the head of patch below.
>From e53c63a8ff00c76f165e371511604f374451627b Mon Sep 17 00:00:00 2001
From: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Date: Thu, 18 Nov 2010 09:18:15 +0900
Subject: [PATCH] CAN : Separate interface register from whole of register structure.
CAN register of Intel PCH EG20T has 2 sets of interface register.
To reduce whole of code size, separate interface register.
As a result, the number of function also can be reduced.
Signed-off-by: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
---
drivers/net/can/pch_can.c | 445 ++++++++++++++++++++-------------------------
1 files changed, 201 insertions(+), 244 deletions(-)
.........
Since I have copied from the patch file directly, whitespace is inserted.
When next resubmitting, I will delete the whiletespace by hand.
---
Thanks,
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
next prev parent reply other threads:[~2010-11-29 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 2:01 [PATCH net-next-2.6 01/19 v5] can: EG20T PCH: Separate Interface Register(IF1/IF2) Tomoya MORINAGA
2010-11-26 9:58 ` Marc Kleine-Budde
2010-11-26 10:04 ` Marc Kleine-Budde
2010-11-29 1:59 ` Tomoya MORINAGA [this message]
2010-11-29 9:22 ` Marc Kleine-Budde
2010-11-29 9:46 ` Tomoya MORINAGA
2010-11-29 10:08 ` Marc Kleine-Budde
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='002201cb8f69$11d30050$66f8800a@maildom.okisemi.com' \
--to=tomoya-linux@dsn.okisemi.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=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