All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] can: bcm: prevent thrtimer UAF in rx path by checking RX_NO_AUTOTIMER
Date: Tue, 5 May 2026 15:42:27 +0100	[thread overview]
Message-ID: <20260505144227.GB2661693@google.com> (raw)
In-Reply-To: <20260427-zealous-booby-from-avalon-c9753c-mkl@pengutronix.de>

On Mon, 27 Apr 2026, Marc Kleine-Budde wrote:

> On 27.04.2026 19:15:29, Oliver Hartkopp wrote:
> > > > Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> > >
> > > I'm a little confused by the SoB.  Does this mean you've applied it?
> > >
> >
> > No. Marc will apply the patch.
> >
> > My SoB is probably not needed in this context.
> 
> ACK
> 
> > But Marc was sometimes asking
> > for it when I commented and discussed patches in the past.
> 
> The rule is: if you post a patch, your S-o-b has to be the last S-o-b in
> the line.
> 
> > I also thought Marc would add the Fixes tag on his own.
> 
> If you add it in the thread, b-4 will pick it up automatically and this
> less work for me :)

Any luck with this one Marc.

This should be send to the -rcs ASAP please.

-- 
Lee Jones

  parent reply	other threads:[~2026-05-05 14:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 10:22 [PATCH 1/1] can: bcm: prevent thrtimer UAF in rx path by checking RX_NO_AUTOTIMER Lee Jones
2026-04-22 12:55 ` Oliver Hartkopp
2026-04-24 19:08   ` Marc Kleine-Budde
2026-04-25  6:49     ` Oliver Hartkopp
2026-04-27 12:40       ` Lee Jones
2026-04-27 17:15         ` Oliver Hartkopp
2026-04-27 17:41           ` Marc Kleine-Budde
2026-04-27 17:58             ` Oliver Hartkopp
2026-04-28  8:57             ` Lee Jones
2026-04-28  9:32               ` Oliver Hartkopp
2026-05-05 14:42             ` Lee Jones [this message]
2026-05-06 12:45 ` 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=20260505144227.GB2661693@google.com \
    --to=lee@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.