Linux CAN drivers development
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: updated candump available in can-utils - Re: pull-request: can-next 2015-04-01
Date: Wed, 01 Apr 2015 13:27:02 +0200	[thread overview]
Message-ID: <551BD606.3040502@hartkopp.net> (raw)
In-Reply-To: <551BC2C0.5000408@pengutronix.de>

If you want to test the new feature:

The latest candump supports the 'join' option with a [j|J] added to the
socket specific filter list:

https://github.com/linux-can/can-utils/commit/1a2467ed29302149d4d1253888ac1f1dfcc11d3f


Feedback & testing is welcome.

Regards,
Oliver

On 01.04.2015 12:04, Marc Kleine-Budde wrote:
> Hello David,
> 
> this is a pull request of 5 patches for net-next/master.
> 
> There are two patches for the ems_usb driver by Gerhard Uttenthaler and
> me, which fix sparse endianess warnings. Oliver Hartkopp adds two
> patches to improve and extend the CAN-ID filter handling on RAW CAN
> sockets. The last patch is by me, it silences an uninitialized variable
> warning in the peak_usb driver.
> 
> Marc
> 
> ---
> 
> The following changes since commit 9911674fcf1f239ff3c87e56177c4826e33dfd95:
> 
>    Merge branch 'ptp-ns_to_timespec64' (2015-03-31 17:19:19 -0400)
> 
> are available in the git repository at:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.1-20150401
> 
> for you to fetch changes up to 79d5eeddd7d23bd4588e370072977928b7075911:
> 
>    can: pcan_usb: pcan_usb_fd_send_cmd(): silence compiler warning about uninitialized var (2015-04-01 11:49:59 +0200)
> 
> ----------------------------------------------------------------
> linux-can-next-for-4.1-20150401
> 
> ----------------------------------------------------------------
> Gerhard Uttenthaler (1):
>        can: ems_usb: fix endianess of CAN ID
> 
> Marc Kleine-Budde (2):
>        can: ems_usb: mark timestamp as little endian
>        can: pcan_usb: pcan_usb_fd_send_cmd(): silence compiler warning about uninitialized var
> 
> Oliver Hartkopp (2):
>        can: fix multiple delivery of a single CAN frame for overlapping CAN filters
>        can: introduce new raw socket option to join the given CAN filters
> 
>   Documentation/networking/can.txt           | 20 ++++++++++--
>   drivers/net/can/usb/ems_usb.c              | 11 +++----
>   drivers/net/can/usb/peak_usb/pcan_usb_fd.c |  2 +-
>   include/uapi/linux/can/raw.h               |  1 +
>   net/can/raw.c                              | 50 ++++++++++++++++++++++++++++++
>   5 files changed, 74 insertions(+), 10 deletions(-)
> 

  reply	other threads:[~2015-04-01 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 10:04 pull-request: can-next 2015-04-01 Marc Kleine-Budde
2015-04-01 11:27 ` Oliver Hartkopp [this message]
2015-04-01 17:58 ` David Miller

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=551BD606.3040502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox