From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2015-06-21
Date: Sun, 21 Jun 2015 19:04:58 +0200 [thread overview]
Message-ID: <1434906299-19452-1-git-send-email-mkl@pengutronix.de> (raw)
Hello David,
this is a, probably too late, pull request for v4.1.
Oliver Hartkopp fixed a bug in the generic CAN frame handling code, which may
lead to loss of CAN frames. It was introduced during v4.1 development.
Please queue via net/master if possible, net-next/master otherwise. I've added
stable on Cc, just in case.
regards,
Marc
---
The following changes since commit 7b48f45797be7c4bdbb772de80efe6bdcd78e81d:
isdn: disable HiSax NetJet driver on microblaze arch (2015-06-21 09:53:01 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-4.1-20150621
for you to fetch changes up to 36c01245eb8046c16eee6431e7dbfbb302635fa8:
can: fix loss of CAN frames in raw_rcv (2015-06-21 18:58:58 +0200)
----------------------------------------------------------------
linux-can-fixes-for-4.1-20150621
----------------------------------------------------------------
Oliver Hartkopp (1):
can: fix loss of CAN frames in raw_rcv
drivers/net/can/dev.c | 5 +++++
drivers/net/can/slcan.c | 1 +
drivers/net/can/vcan.c | 3 +++
net/can/af_can.c | 6 +++++-
4 files changed, 14 insertions(+), 1 deletion(-)
next reply other threads:[~2015-06-21 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 17:04 Marc Kleine-Budde [this message]
2015-06-21 17:04 ` [PATCH] can: fix loss of CAN frames in raw_rcv Marc Kleine-Budde
2015-06-23 13:43 ` pull-request: can 2015-06-21 David Miller
2015-06-30 19:31 ` missing in stable 4.1.1 - was " Oliver Hartkopp
2015-06-30 20:07 ` Greg KH
2015-06-30 20:28 ` Oliver Hartkopp
2015-06-30 21:04 ` Greg KH
2015-06-30 21:20 ` 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=1434906299-19452-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=netdev@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).