From: Wolfgang Grandegger <wg@grandegger.com>
To: David Miller <davem@davemloft.net>
Cc: vapier@gentoo.org, urs.thuermann@volkswagen.de,
linux-kernel@vger.kernel.org, barry.song@analog.com,
socketcan-core@lists.berlios.de, oliver.hartkopp@volkswagen.de,
stable-review@kernel.org, stable@kernel.org
Subject: Re: [PATCH] can: fix bfin_can build error after alloc_candev() change
Date: Mon, 08 Mar 2010 21:47:58 +0100 [thread overview]
Message-ID: <4B95627E.1050301@grandegger.com> (raw)
In-Reply-To: <20100308.121445.71193029.davem@davemloft.net>
David Miller wrote:
> From: Wolfgang Grandegger <wg@grandegger.com>
> Date: Mon, 08 Mar 2010 20:47:44 +0100
>
>> Mike Frysinger wrote:
>>> From: Barry Song <barry.song@analog.com>
>>>
>>> Looks like commit a6e4bc530403 didn't include updates to drivers so the
>>> Blackfin CAN driver fails to build now.
>>>
>>> Signed-off-by: Barry Song <barry.song@analog.com>
>>> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>> Oops, it did include updates for the drivers but at that time the bfin
>> driver was not yet mainline but somewhere in the patch pipeline.
>>
>> Acked-by: Wolfgang Grandegger <wg@grandegger.com>
>
> Applied.
>
> Wolfgang et al., can we add netdev to the MAINTAINERS entry
> for CAN stuff so that I don't miss stuff like this?
I see. Just sent a patch for net-2.6 adding "L: netdev@vger.kernel.org".
Wolfgang.
prev parent reply other threads:[~2010-03-08 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 16:35 [PATCH] can: fix bfin_can build error after alloc_candev() change Mike Frysinger
2010-03-08 19:47 ` Wolfgang Grandegger
2010-03-08 20:14 ` David Miller
2010-03-08 20:47 ` Wolfgang Grandegger [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=4B95627E.1050301@grandegger.com \
--to=wg@grandegger.com \
--cc=barry.song@analog.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=socketcan-core@lists.berlios.de \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=urs.thuermann@volkswagen.de \
--cc=vapier@gentoo.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.