From: Eric Dumazet <eric.dumazet@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>,
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 1/17 v2] can: EG20T PCH: Separate Interface Register(IF1/IF2)
Date: Wed, 24 Nov 2010 11:54:25 +0100 [thread overview]
Message-ID: <1290596065.3464.30.camel@edumazet-laptop> (raw)
In-Reply-To: <4CECEC85.1050009@pengutronix.de>
Le mercredi 24 novembre 2010 à 11:44 +0100, Marc Kleine-Budde a écrit :
> 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.
>
> > Signed-off-by: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
> > ---
> > drivers/net/can/pch_can.c | 442 ++++++++++++++++++++-------------------------
> > 1 files changed, 198 insertions(+), 244 deletions(-)
> >
> > diff --git a/drivers/net/can/pch_can.c b/drivers/net/can/pch_can.c
> > index 238622a..143f100 100644
> > --- a/drivers/net/can/pch_can.c
> > +++ b/drivers/net/can/pch_can.c
> > @@ -102,6 +102,9 @@
> > #define PCH_MSK_CTRL_IE_SIE_EIE 0x07
> > #define PCH_COUNTER_LIMIT 10
> >
> > +#define PCH_RX_IFREG 0
> > +#define PCH_TX_IFREG 1
>
> Please make this enum _here_, not in a later patch.
>
[then, huge part deleted, containing no review, spent some time to
discover this...]
Marc, could you please dont include the whole mail in your replies ?
We have a high Noise Rate on this topic already.
Thanks
next prev parent reply other threads:[~2010-11-24 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CECBFE3.8030402@dsn.okisemi.com>
[not found] ` <4CECBFE3.8030402-ECg8zkTtlr0C6LszWs/t0g@public.gmane.org>
2010-11-24 10:44 ` [PATCH net-next-2.6 1/17 v2] can: EG20T PCH: Separate Interface Register(IF1/IF2) Marc Kleine-Budde
2010-11-24 10:54 ` Eric Dumazet [this message]
2010-11-24 10:58 ` Tomoya MORINAGA
[not found] ` <4CECEC85.1050009-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-11-24 16:55 ` David Miller
[not found] ` <20101124.085554.193704043.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-11-24 16:57 ` David Miller
2010-11-24 7:33 Tomoya MORINAGA
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=1290596065.3464.30.camel@edumazet-laptop \
--to=eric.dumazet@gmail.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=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