From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de
Subject: [PATCH net 0/5] pull-request: can 2024-06-21
Date: Fri, 21 Jun 2024 13:23:35 +0200 [thread overview]
Message-ID: <20240621121739.434355-1-mkl@pengutronix.de> (raw)
Hello netdev-team,
this is a pull request of 5 patches for net/master.
The first patch is by Oleksij Rempel, it enhances the error handling
for tightly received RTS message in the j1939 protocol.
Shigeru Yoshida's patch fixes a kernel information leak in
j1939_send_one() in the j1939 protocol.
Followed by a patch by Oleksij Rempel for the j1939 protocol, to
properly recover from a CAN bus error during BAM transmission.
A patch by Chen Ni properly propagates errors in the kvaser_usb
driver.
The last patch is by Vitor Soares, that fixes an infinite loop in the
mcp251xfd driver is SPI async sending fails during xmit.
regards,
Marc
---
The following changes since commit 8851346912a1fa33e7a5966fe51f07313b274627:
net: stmmac: Assign configured channel value to EXTTS event (2024-06-20 11:56:03 +0200)
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-6.10-20240621
for you to fetch changes up to d8fb63e46c884c898a38f061c2330f7729e75510:
can: mcp251xfd: fix infinite loop when xmit fails (2024-06-21 10:50:20 +0200)
----------------------------------------------------------------
linux-can-fixes-for-6.10-20240621
----------------------------------------------------------------
Chen Ni (1):
can: kvaser_usb: fix return value for hif_usb_send_regout
Oleksij Rempel (2):
net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new
net: can: j1939: recover socket queue on CAN bus error during BAM transmission
Shigeru Yoshida (1):
net: can: j1939: Initialize unused data in j1939_send_one()
Vitor Soares (1):
can: mcp251xfd: fix infinite loop when xmit fails
drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c | 14 +++++-
drivers/net/can/spi/mcp251xfd/mcp251xfd-tx.c | 55 ++++++++++++++++++++----
drivers/net/can/spi/mcp251xfd/mcp251xfd.h | 5 +++
drivers/net/can/usb/kvaser_usb/kvaser_usb_core.c | 2 +-
net/can/j1939/main.c | 6 +--
net/can/j1939/transport.c | 21 ++++++++-
6 files changed, 86 insertions(+), 17 deletions(-)
next reply other threads:[~2024-06-21 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 11:23 Marc Kleine-Budde [this message]
2024-06-21 11:23 ` [PATCH net 1/5] net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new Marc Kleine-Budde
2024-06-22 1:20 ` patchwork-bot+netdevbpf
2024-06-21 11:23 ` [PATCH net 2/5] net: can: j1939: Initialize unused data in j1939_send_one() Marc Kleine-Budde
2024-06-21 11:23 ` [PATCH net 3/5] net: can: j1939: recover socket queue on CAN bus error during BAM transmission Marc Kleine-Budde
2024-06-21 11:23 ` [PATCH net 4/5] can: kvaser_usb: fix return value for hif_usb_send_regout Marc Kleine-Budde
2024-06-21 11:23 ` [PATCH net 5/5] can: mcp251xfd: fix infinite loop when xmit fails 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=20240621121739.434355-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--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).