From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: upcoming pull reqeust
Date: Fri, 25 Jan 2013 16:55:03 +0100 [thread overview]
Message-ID: <5102AAD7.3040403@hartkopp.net> (raw)
In-Reply-To: <50FF0C9C.3030207@pengutronix.de>
On 22.01.2013 23:03, Marc Kleine-Budde wrote:
> The patches are in the for-davem branch in the linux-can-next repo at
> gitorious:
>
> https://gitorious.org/linux-can/linux-can-next/commits/for-davem
>
> Bernd Krumboeck (2):
> can: usb_8dev: Add support for USB2CAN interface from 8 devices
> can: usb_8dev: add LED trigger support
>
> Fabio Baltieri (7):
> can: add tx/rx LED trigger support
> can: flexcan: add LED trigger support
> can: at91_can: add LED trigger support
> can: ti_hecc: add LED trigger support
> can: c_can: add LED trigger support
> can: mcp251x: add LED trigger support
> can: sja1000: add LED trigger support
>
> Kurt Van Dijck (2):
> can: export a safe netdev_priv wrapper for candev
> can: rename LED trigger name on netdev renames
>
> Marc Kleine-Budde (4):
> can: Kconfig: convert 'depends on CAN' into 'if CAN...endif' block
> can: Kconfig: convert 'depends on CAN_DEV' into 'if CAN_DEV...endif' block
> can: Kconfig: switch on all CAN protocolls by default
> can: sja1000: correct indention of Kconfig help text
>
> Oliver Hartkopp (4):
> can: add private data space for CAN sk_buffs
> can: gw: make routing to the incoming CAN interface configurable
> can: gw: add a variable limit for CAN frame routings
> can: gw: indicate and count deleted frames due to misconfiguration
>
>
> Comments?
>
What's you plan when to send the pull request to Dave?
Btw. have you seen the 3 c_can fixes from Olivier Sobrie for the net/stable
tree from 2013-01-18? They all look correct.
Regards,
Oliver
next prev parent reply other threads:[~2013-01-25 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 20:58 upcoming pull reqeust Marc Kleine-Budde
2013-01-19 13:34 ` Oliver Hartkopp
2013-01-22 22:03 ` Marc Kleine-Budde
2013-01-25 15:55 ` Oliver Hartkopp [this message]
2013-01-26 16:09 ` Marc Kleine-Budde
2013-01-26 16:35 ` Marc Kleine-Budde
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=5102AAD7.3040403@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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.