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>,
"Christian Pellegrin" <chripell@fsfe.org>,
<linux-kernel@vger.kernel.org>, <yong.y.wang@intel.com>,
<socketcan-core@lists.berlios.de>, <kok.howg.ewe@intel.com>,
<joel.clark@intel.com>, "David S. Miller" <davem@davemloft.net>,
"Wolfgang Grandegger" <wg@grandegger.com>, <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 18:46:01 +0900 [thread overview]
Message-ID: <001501cb8faa$3cc7f220$66f8800a@maildom.okisemi.com> (raw)
In-Reply-To: 4CF370D3.7020606@pengutronix.de
On Monday, November 29, 2010 6:22 PM, Marc Kleine-Budde wrote :
> Maybe your patch description in git commit is unusual. It should be a
> one line patch subject, followed by a blank line, then a multi line
> patch description.
Adding blank line below subject line, I could confirm
whitespace is not inserted.
Thank you.
----
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
next prev parent reply other threads:[~2010-11-29 9:46 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
2010-11-29 9:22 ` Marc Kleine-Budde
2010-11-29 9:46 ` Tomoya MORINAGA [this message]
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='001501cb8faa$3cc7f220$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