From: David Miller <davem@davemloft.net>
To: wg@grandegger.com
Cc: Socketcan-core@lists.berlios.de, Netdev@vger.kernel.org,
Devicetree-discuss@lists.ozlabs.org,
Linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net-next v4 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x
Date: Fri, 08 Jan 2010 01:02:33 -0800 (PST) [thread overview]
Message-ID: <20100108.010233.267965992.davem@davemloft.net> (raw)
In-Reply-To: <4B46F3D2.8070102@grandegger.com>
From: Wolfgang Grandegger <wg@grandegger.com>
Date: Fri, 08 Jan 2010 09:58:58 +0100
> David Miller wrote:
>> From: Wolfgang Grandegger <wg@grandegger.com>
>> Date: Thu, 7 Jan 2010 20:43:05 +0100
>>
>>> This patch series adds support for the MPC512x from Freescale to the
>>> mpc5xxx_can MSCAN driver. It has been tested on a MPC5121 and MPC5200B
>>> board.
>>
>> So are these ready to go or should I wait for another round
>> of review? :-)
>
>>From my point of view they can go in now, finally.
Ok, all applied to net-next-2.6, thanks.
prev parent reply other threads:[~2010-01-08 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 19:43 [PATCH net-next v4 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x Wolfgang Grandegger
2010-01-07 19:43 ` [PATCH net-next v4 1/3] can: mscan: fix improper return if dlc < 8 in start_xmit function Wolfgang Grandegger
2010-01-07 19:43 ` [PATCH net-next v4 2/3] can: mscan-mpc5xxx: add support for the MPC512x processor Wolfgang Grandegger
2010-01-07 19:43 ` [PATCH net-next v4 3/3] powerpc/mpc5xxx: add OF platform binding doc for FSL MSCAN devices Wolfgang Grandegger
2010-01-08 8:41 ` [PATCH net-next v4 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x David Miller
2010-01-08 8:58 ` Wolfgang Grandegger
2010-01-08 9:02 ` 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=20100108.010233.267965992.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Devicetree-discuss@lists.ozlabs.org \
--cc=Linuxppc-dev@lists.ozlabs.org \
--cc=Netdev@vger.kernel.org \
--cc=Socketcan-core@lists.berlios.de \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).