From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: tomoya-linux@dsn.okisemi.com, wg@grandegger.com,
w.sang@pengutronix.de, chripell@fsfe.org, 21cnbao@gmail.com,
sameo@linux.intel.com, socketcan-core@lists.berlios.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
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 1/17 v2] can: EG20T PCH: Separate Interface Register(IF1/IF2)
Date: Wed, 24 Nov 2010 08:57:04 -0800 (PST) [thread overview]
Message-ID: <20101124.085704.226785473.davem@davemloft.net> (raw)
In-Reply-To: <20101124.085554.193704043.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Wed, 24 Nov 2010 08:55:54 -0800 (PST)
> From: Marc Kleine-Budde <mkl@pengutronix.de>
> Date: Wed, 24 Nov 2010 11:44:21 +0100
>
>> On 11/24/2010 08:33 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.
>>
>> I failed to apply your series to david's net-2.6/master. Please resubmit.
>
> It applies to net-next-2.6 since that is where I applied his previous
> two patches.
And geese Marc, I just noticed he even said "net-next-2.6" explicitly
in the subject lines.... :-/
prev parent reply other threads:[~2010-11-24 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 7:33 [PATCH net-next-2.6 1/17 v2] can: EG20T PCH: Separate Interface Register(IF1/IF2) Tomoya MORINAGA
2010-11-24 10:44 ` Marc Kleine-Budde
2010-11-24 10:54 ` Eric Dumazet
2010-11-24 10:58 ` Tomoya MORINAGA
2010-11-24 16:55 ` David Miller
2010-11-24 16:57 ` David Miller [this message]
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=20101124.085704.226785473.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=21cnbao@gmail.com \
--cc=andrew.chih.howe.khor@intel.com \
--cc=chripell@fsfe.org \
--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=tomoya-linux@dsn.okisemi.com \
--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