linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH v2 0/5] Add support for CAN FD to broadcast manager (CAN_BCM)
Date: Mon, 30 May 2016 20:36:25 +0200	[thread overview]
Message-ID: <1464633390-24299-1-git-send-email-socketcan@hartkopp.net> (raw)

This series adds the capability for the CAN broadcast manager to handle
CAN FD frames analogue to the CAN frames. It allows sending as well as all
known data filtering functions (including multiplex filtering).

Changes in v2:
Introduce a helper variable cfsiz to prevent multiple CFSIZ(op) operations
in bcm_rx_handler() (patch 4/5).

Oliver Hartkopp (5):
  can: bcm: fix indention style
  can: bcm: use CAN frame instead of can_frame in comments
  can: bcm: unify bcm_msg_head handling and prepare function parameters
  can: bcm: add support for CAN FD frames
  can: bcm: add documentation for CAN FD support

 Documentation/networking/can.txt |  22 +++
 include/uapi/linux/can/bcm.h     |   1 +
 net/can/bcm.c                    | 313 +++++++++++++++++++++++----------------
 3 files changed, 206 insertions(+), 130 deletions(-)

-- 
2.8.1


             reply	other threads:[~2016-05-30 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-30 18:36 Oliver Hartkopp [this message]
2016-05-30 18:36 ` [PATCH v2 1/5] can: bcm: fix indention style Oliver Hartkopp
2016-05-30 18:36 ` [PATCH v2 2/5] can: bcm: use CAN frame instead of can_frame in comments Oliver Hartkopp
2016-05-30 18:36 ` [PATCH v2 3/5] can: bcm: unify bcm_msg_head handling and prepare function parameters Oliver Hartkopp
2016-05-30 18:36 ` [PATCH v2 4/5] can: bcm: add support for CAN FD frames Oliver Hartkopp
2016-05-30 18:36 ` [PATCH v2 5/5] can: bcm: add documentation for CAN FD support Oliver Hartkopp
2016-05-30 18:43 ` Request for testing - Re: [PATCH v2 0/5] Add support for CAN FD to broadcast manager (CAN_BCM) Oliver Hartkopp

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=1464633390-24299-1-git-send-email-socketcan@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).