From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
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: Fri, 26 Nov 2010 11:04:59 +0100 [thread overview]
Message-ID: <4CEF864B.6080207@pengutronix.de> (raw)
In-Reply-To: <4CEF84BE.7000101@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On 11/26/2010 10:58 AM, Marc Kleine-Budde wrote:
> On 11/26/2010 03:01 AM, Tomoya MORINAGA wrote:
>> 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.
>
> nitpick: it's unusual to have leading whitespace in the patch description.
maybe it's a problem of your mailer.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-11-26 10:05 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 [this message]
2010-11-29 1:59 ` Tomoya MORINAGA
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=4CEF864B.6080207@pengutronix.de \
--to=mkl@pengutronix.de \
--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=netdev@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=sameo@linux.intel.com \
--cc=socketcan-core@lists.berlios.de \
--cc=tomoya-linux@dsn.okisemi.com \
--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