mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Vincent Mailhol" <mailhol@kernel.org>,
	linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Stéphane Grosjean" <s.grosjean@peak-system.fr>,
	"Stéphane Grosjean" <stephane.grosjean@free.fr>
Subject: can-next - Re: [PATCH v3] can: peak_usb: Add bus error reporting for the PCAN-USB FD family
Date: Wed, 30 Sep 2026 11:59:03 +0200	[thread overview]
Message-ID: <f265f6ce-5a3d-499f-aece-09aa16970487@hartkopp.net> (raw)
In-Reply-To: <20260930-wondrous-unbeatable-guan-f7b2e1-mkl@pengutronix.de>

Hi Marc,

On 30.09.26 11:10, Marc Kleine-Budde wrote:
> On 30.09.2026 10:44:33, Stéphane Grosjean wrote:
>> From: Stéphane Grosjean <s.grosjean@peak-system.fr>
>>
>> CAN bus error reporting is currently missing for all PEAK-System
>> USB-to-CAN FD devices. Add support for reporting bus errors by enabling
>> bus error notifications in the firmware for each CAN channel. Parsing of
>> the entire URB is aborted if the firmware reports an invalid channel.
>>
>> Signed-off-by: Stéphane Grosjean <s.grosjean@peak-system.fr>
> 
> Good work. Applied to linux-can-next.

There's nothing to see from your patches - neither in

https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/

nor in

https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git/

where you sent the PRs to the netdev team yesterday.

Btw do you have those can-next patches still on your radar?

[can-next v2] can: proc: remove pointers from CAN specific proc output
https://lore.kernel.org/linux-can/20260815103400.117175-1-socketcan@hartkopp.net/

[can-next] can: remove Softing CANcard driver
https://lore.kernel.org/linux-can/20260815103428.117201-1-socketcan@hartkopp.net/

[PATCH can-next] can: raw: remove redundant NULL check before netdev_hold()
https://lore.kernel.org/linux-can/20260831052031.902699-1-ekffu200098@gmail.com/

Best regards,
Oliver


  reply	other threads:[~2026-09-30 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  8:44 Stéphane Grosjean
2026-09-30  9:10 ` Marc Kleine-Budde
2026-09-30  9:59   ` Oliver Hartkopp [this message]
2026-10-03  4:57 ` netdev-bot+sashiko

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=f265f6ce-5a3d-499f-aece-09aa16970487@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=s.grosjean@peak-system.fr \
    --cc=stephane.grosjean@free.fr \
    /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

all inboxes | Powered by JetHome®