netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	linux-can@vger.kernel.org, kernel@pengutronix.de,
	o.rempel@pengutronix.de,
	syzbot+daa36413a5cedf799ae4@syzkaller.appspotmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net 1/5] net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new
Date: Sat, 22 Jun 2024 01:20:31 +0000	[thread overview]
Message-ID: <171901923109.1383.11282114913538537501.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240621121739.434355-2-mkl@pengutronix.de>

Hello:

This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:

On Fri, 21 Jun 2024 13:23:36 +0200 you wrote:
> From: Oleksij Rempel <o.rempel@pengutronix.de>
> 
> This patch enhances error handling in scenarios with RTS (Request to
> Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE
> backtraces with a new error handling method. This provides clearer error
> messages and allows for the early termination of problematic sessions.
> Previously, sessions were only released at the end of j1939_xtp_rx_rts().
> 
> [...]

Here is the summary with links:
  - [net,1/5] net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new
    https://git.kernel.org/netdev/net/c/d3e2904f71ea
  - [net,2/5] net: can: j1939: Initialize unused data in j1939_send_one()
    https://git.kernel.org/netdev/net/c/b7cdf1dd5d2a
  - [net,3/5] net: can: j1939: recover socket queue on CAN bus error during BAM transmission
    https://git.kernel.org/netdev/net/c/9ad1da14ab3b
  - [net,4/5] can: kvaser_usb: fix return value for hif_usb_send_regout
    https://git.kernel.org/netdev/net/c/0d34d8163fd8
  - [net,5/5] can: mcp251xfd: fix infinite loop when xmit fails
    https://git.kernel.org/netdev/net/c/d8fb63e46c88

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-06-22  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 11:23 [PATCH net 0/5] pull-request: can 2024-06-21 Marc Kleine-Budde
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 [this message]
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=171901923109.1383.11282114913538537501.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+daa36413a5cedf799ae4@syzkaller.appspotmail.com \
    /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).