linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: [PATCH 0/4] CAN sk_buff and can-gw enhancements
Date: Thu, 17 Jan 2013 18:43:36 +0100	[thread overview]
Message-ID: <50F83848.4090006@hartkopp.net> (raw)

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

Regards,
Oliver

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

 drivers/net/can/dev.c       |    8 ++++-
 drivers/net/can/slcan.c     |    8 ++++-
 include/linux/can/skb.h     |   35 ++++++++++++++++++++
 include/uapi/linux/can/gw.h |    2 ++
 net/can/bcm.c               |   12 +++++--
 net/can/gw.c                |   74 +++++++++++++++++++++++++++++++++----------
 net/can/raw.c               |    8 +++--
 7 files changed, 124 insertions(+), 23 deletions(-)
 create mode 100644 include/linux/can/skb.h

-- 
1.7.10.4


             reply	other threads:[~2013-01-17 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 17:43 Oliver Hartkopp [this message]
2013-01-22 21:41 ` [PATCH 0/4] CAN sk_buff and can-gw enhancements Marc Kleine-Budde
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=50F83848.4090006@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.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 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).