From: Wolfram Sang <w.sang@pengutronix.de>
To: Wolfgang Grandegger <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 v2 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x
Date: Wed, 6 Jan 2010 15:45:31 +0100 [thread overview]
Message-ID: <20100106144531.GD5299@pengutronix.de> (raw)
In-Reply-To: <4B449EB0.5090107@grandegger.com>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
> Wolfram, is it OK from your point of view now? I will roll out v3 after
> some more thorough testing tomorrow.
It still works here and, as I see it, all issues were resolved as discussed.
Thanks,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-01-06 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 19:20 [PATCH net-next v2 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x Wolfgang Grandegger
2010-01-05 19:20 ` [PATCH net-next v2 1/3] can: mscan: fix improper return if dlc < 8 in start_xmit function Wolfgang Grandegger
2010-01-05 19:20 ` [PATCH net-next v2 2/3] can: mscan-mpc5xxx: add support for the MPC512x processor Wolfgang Grandegger
2010-01-05 19:20 ` [PATCH net-next v2 3/3] powerpc/mpc5xxx: add OF platform binding doc for FSL MSCAN devices Wolfgang Grandegger
2010-01-06 14:31 ` [PATCH net-next v2 0/3] can: mscan-mpc5xxx: add support for the Freescale MPC512x Wolfgang Grandegger
2010-01-06 14:45 ` Wolfram Sang [this message]
2010-01-06 15:22 ` Wolfgang Grandegger
2010-01-06 15:59 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2010-01-05 19:19 Wolfgang Grandegger
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=20100106144531.GD5299@pengutronix.de \
--to=w.sang@pengutronix.de \
--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).