From: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: [PATCH 0/9] can: don't copy data to rx'ed RTR frames
Date: Sat, 25 Dec 2010 15:40:25 +0100 [thread overview]
Message-ID: <1293288034-22428-1-git-send-email-mkl@pengutronix.de> (raw)
Hello,
this series of patches changes the can driver's RX path. If a RTR frame is
received no data is copied.
As discussed on socketcan-core:
https://lists.berlios.de/pipermail/socketcan-core/2010-October/004836.html
cheers,
Marc
---
The following changes since commit e1928c86c4829703b800c81cc9edc939b5634e6f:
cnic: Add FCoE support on 57712 (2010-12-23 11:44:34 -0800)
are available in the git repository at:
git://git.pengutronix.de/git/mkl/linux-2.6.git public/can/rtr-for-net-next
Marc Kleine-Budde (9):
can: at91_can: don't copy data to rx'ed RTR frames
can: bfin_can: don't copy data to rx'ed RTR frames
can: flexcan: don't copy data to rx'ed RTR frames
can: sja1000: don't copy data to rx'ed RTR frames
can: mcp251x: don't copy data to rx'ed RTR frames
can: ti_hecc: don't copy data to rx'ed RTR frames
can: janz-ican3: cleanup of ican3_to_can_frame and can_frame_to_ican3
can: janz-ican3: don't copy data to rx'ed RTR frames
can: pch_can: don't copy data to rx'ed RTR frames
drivers/net/can/at91_can.c | 10 ++++++----
drivers/net/can/bfin_can.c | 17 +++++++++--------
drivers/net/can/flexcan.c | 10 ++++++----
drivers/net/can/janz-ican3.c | 26 +++++++++++++++-----------
drivers/net/can/mcp251x.c | 3 ++-
drivers/net/can/pch_can.c | 15 ++++++++-------
drivers/net/can/sja1000/sja1000.c | 7 +++----
drivers/net/can/ti_hecc.c | 18 ++++++++++--------
8 files changed, 59 insertions(+), 47 deletions(-)
next reply other threads:[~2010-12-25 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 14:40 Marc Kleine-Budde [this message]
2010-12-25 14:40 ` [PATCH 2/9] can: bfin_can: don't copy data to rx'ed RTR frames Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 4/9] can: sja1000: " Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 5/9] can: mcp251x: " Marc Kleine-Budde
[not found] ` <1293288034-22428-1-git-send-email-mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-12-25 14:40 ` [PATCH 1/9] can: at91_can: " Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 3/9] can: flexcan: " Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 6/9] can: ti_hecc: " Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 7/9] can: janz-ican3: cleanup of ican3_to_can_frame and can_frame_to_ican3 Marc Kleine-Budde
[not found] ` <1293288034-22428-8-git-send-email-mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-12-26 3:32 ` David Miller
2010-12-25 14:40 ` [PATCH 8/9] can: janz-ican3: don't copy data to rx'ed RTR frames Marc Kleine-Budde
2010-12-25 14:40 ` [PATCH 9/9] can: pch_can: " Marc Kleine-Budde
[not found] ` <1293288034-22428-10-git-send-email-mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-12-25 15:52 ` Oliver Hartkopp
[not found] ` <4D161334.3090100-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2010-12-25 16:25 ` 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=1293288034-22428-1-git-send-email-mkl@pengutronix.de \
--to=mkl-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.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).