From: David Miller <davem@davemloft.net>
To: wg@grandegger.com
Cc: netdev@vger.kernel.org, socketcan-core@lists.berlios.de,
urs.thuermann@volkswagen.de, oliver.hartkopp@volkswagen.de
Subject: Re: [PATCH net-next] can: add can_free_echo_skb() for upcoming drivers
Date: Fri, 04 Sep 2009 02:13:50 -0700 (PDT) [thread overview]
Message-ID: <20090904.021350.234672852.davem@davemloft.net> (raw)
In-Reply-To: <4AA0C692.5000003@grandegger.com>
From: Wolfgang Grandegger <wg@grandegger.com>
Date: Fri, 04 Sep 2009 09:49:38 +0200
> David Miller wrote:
>> Can a CAN expert please review these patches? They are rotting
>> in patchwork and I want to move forward with them somehow.I'
>
> I'm maintaining the CAN device drivers interface and drivers as listed
> in MAINTAINERS. Though, these patches have already the official blessing.
My bad :-) I'll apply these then.
> Do you want me to setup a git repository "can-next-2.6" where you can
> pull from? So far, not that much can-drv patches have been posted to
> this list.
You can do that in the future if you like, sure. But it is not a
requirement, as with the rate you guys send things I am handling it
efficiently using patchwork.
next prev parent reply other threads:[~2009-09-04 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 15:26 [PATCH net-next] can: add can_free_echo_skb() for upcoming drivers Wolfgang Grandegger
2009-09-04 3:46 ` David Miller
[not found] ` <20090903.204641.193482962.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-09-04 5:27 ` Oliver Hartkopp
2009-09-04 7:49 ` Wolfgang Grandegger
2009-09-04 9:13 ` David Miller [this message]
[not found] ` <20090904.021350.234672852.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-09-04 14:34 ` 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=20090904.021350.234672852.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=socketcan-core@lists.berlios.de \
--cc=urs.thuermann@volkswagen.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).