From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [PATCH 0/4] CAN sk_buff and can-gw enhancements
Date: Tue, 22 Jan 2013 22:41:53 +0100 [thread overview]
Message-ID: <50FF07A1.1070909@pengutronix.de> (raw)
In-Reply-To: <50F83848.4090006@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On 01/17/2013 06:43 PM, Oliver Hartkopp wrote:
> From 0cb44d2bda7d3aeb96ce45eb7ee24a139bf40f78 Mon Sep 17 00:00:00 2001
> From: Oliver Hartkopp <socketcan@hartkopp.net>
> Date: Thu, 17 Jan 2013 17:51:48 +0100
> Subject: [PATCH 0/4] CAN sk_buff and can-gw enhancements
>
> Hi all,
>
> after the discussion with DaveM about the skb_iif usage here's my alternative
> to support the new can-gw functionalities:
>
> - make routing to the incoming CAN interface configurable
> - add a variable limit for CAN frame routings
> - indicate and count deleted frames due to misconfiguration
>
> I added some private space to CAN sk_buffs. See commit messages.
>
> It can be pulled from the cangw branch of ollis-can-next:
>
> https://gitorious.org/~hartkopp/linux-can/ollis-can-next/commits/cangw
Applied.
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: 263 bytes --]
next prev parent reply other threads:[~2013-01-22 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 17:43 [PATCH 0/4] CAN sk_buff and can-gw enhancements Oliver Hartkopp
2013-01-22 21:41 ` Marc Kleine-Budde [this message]
2013-01-22 22:12 ` Marc Kleine-Budde
2013-01-23 9:14 ` Oliver Hartkopp
2013-01-23 9:20 ` 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=50FF07A1.1070909@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).