From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
linux-can@vger.kernel.org, Anant Gole <anantgole@ti.com>,
Chris Elston <celston@katalix.com>,
Sebastian Haas <haas@ems-wuensche.com>,
Matthias Fuchs <matthias.fuchs@esd.eu>,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH net-next] can: replace the dev_dbg/info/err/... with the new netdev_xxx macros
Date: Wed, 01 Feb 2012 17:11:37 +0100 [thread overview]
Message-ID: <4F296439.6080606@pengutronix.de> (raw)
In-Reply-To: <201202011051.45893.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On 02/01/2012 04:51 PM, Mike Frysinger wrote:
>> Is there somebody else we should inform about patches for the bfin_can
>> driver. Maybe Mike (now on CC)?
>
> for Blackfin devs, you can CC uclinux-dist-devel@blackfin.uclinux.org to get the
> relevant people. Barry Song no longer works for ADI.
>
> the bfin_can.c changes in here look fine to me (not that i tried compiling them,
> but looks straight forward enough):
> http://thread.gmane.org/gmane.linux.can/251/focus=257
>
> Acked-by: Mike Frysinger <vapier@gentoo.org>
tnx
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2012-02-01 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 15:27 [PATCH net-next] can: replace the dev_dbg/info/err/... with the new netdev_xxx macros Wolfgang Grandegger
2011-12-17 15:12 ` Sebastian Haas
2012-01-31 22:02 ` Marc Kleine-Budde
2012-02-01 10:12 ` Wolfgang Grandegger
2012-02-01 15:51 ` Mike Frysinger
2012-02-01 16:11 ` Marc Kleine-Budde [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=4F296439.6080606@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anantgole@ti.com \
--cc=celston@katalix.com \
--cc=haas@ems-wuensche.com \
--cc=linux-can@vger.kernel.org \
--cc=matthias.fuchs@esd.eu \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
--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).