From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp via B4 Relay
<devnull+socketcan.hartkopp.net@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Urs Thuermann <urs.thuermann@volkswagen.de>,
Vincent Mailhol <mailhol@kernel.org>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+75e5e4ae00c3b4bb544e@syzkaller.appspotmail.com
Subject: Re: [PATCH v3 2/3] can: bcm: add locking when updating filter and timer values
Date: Mon, 23 Mar 2026 10:46:13 +0100 [thread overview]
Message-ID: <afec0eb7-ca32-43ba-8a32-3bd9aedcb030@hartkopp.net> (raw)
In-Reply-To: <20260323-valiant-whispering-buzzard-3e3471-mkl@pengutronix.de>
On 23.03.26 10:42, Marc Kleine-Budde wrote:
> On 02.03.2026 11:21:38, Marc Kleine-Budde wrote:
>> The nipa/ai-review bot found these problems:
>>
>> | https://netdev-ai.bots.linux.dev/ai-review.html?id=873e6dfb-7d8e-4f4d-98ef-a89fcedb701a
>
> I think this patch is the only one of this series, which is still open,
> right?
>
Yes, it is still open.
I'll look at it soon, but it should not delay the other fixes that are
currently agreed.
Best regards,
Oliver
next prev parent reply other threads:[~2026-03-23 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:51 [PATCH v3 0/3] can: bcm: add/fix locking for config updates at runtime Oliver Hartkopp via B4 Relay
2026-02-19 16:51 ` [PATCH v3 1/3] can: bcm: fix locking for bcm_op runtime updates Oliver Hartkopp via B4 Relay
2026-02-19 16:51 ` [PATCH v3 2/3] can: bcm: add locking when updating filter and timer values Oliver Hartkopp via B4 Relay
2026-03-02 10:21 ` Marc Kleine-Budde
2026-03-23 9:42 ` Marc Kleine-Budde
2026-03-23 9:46 ` Oliver Hartkopp [this message]
2026-02-19 16:51 ` [PATCH v3 3/3] can: statistics: add missing atomic access in hot path Oliver Hartkopp via B4 Relay
2026-03-02 10:22 ` 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=afec0eb7-ca32-43ba-8a32-3bd9aedcb030@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=devnull+socketcan.hartkopp.net@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=syzbot+75e5e4ae00c3b4bb544e@syzkaller.appspotmail.com \
--cc=urs.thuermann@volkswagen.de \
/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