Linux bluetooth development
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Pauli Virtanen <pav@iki.fi>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: fix wrong identifier in __set_ack_timer()
Date: Sun, 30 Aug 2026 01:24:50 +0200	[thread overview]
Message-ID: <e4f4931b-c930-4efd-9bbb-9f83d6ddf360@molgen.mpg.de> (raw)
In-Reply-To: <efd26a64addcb562db0745aa4e0a8d2252be1d65.1788016177.git.pav@iki.fi>

Dear Pauli,


Thank you for your patch.

Am 29.08.26 um 17:13 schrieb Pauli Virtanen:
> __set_ack_timer(c) has chan->ack_timer instead of c->ack_timer like the
> other macros.
> 
> Fix it to use the timer corresponding to the macro argument.  In current
> code this is only called as __set_ack_timer(chan) so this has no runtime
> impact.
> 
> Signed-off-by: Pauli Virtanen <pav@iki.fi>
> ---
> 
> Notes:
>      Saw this one in Sashiko trace.
> 
>   include/net/bluetooth/l2cap.h | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index 69d193fee351..99c07f1278a0 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -873,8 +873,8 @@ static inline bool l2cap_clear_timer(struct l2cap_chan *chan,
>   #define __clear_chan_timer(c) l2cap_clear_timer(c, &c->chan_timer)
>   #define __clear_retrans_timer(c) l2cap_clear_timer(c, &c->retrans_timer)
>   #define __clear_monitor_timer(c) l2cap_clear_timer(c, &c->monitor_timer)
> -#define __set_ack_timer(c) l2cap_set_timer(c, &chan->ack_timer, \
> -		msecs_to_jiffies(L2CAP_DEFAULT_ACK_TO));
> +#define __set_ack_timer(c) l2cap_set_timer(c, &c->ack_timer, \
> +		msecs_to_jiffies(L2CAP_DEFAULT_ACK_TO))
>   #define __clear_ack_timer(c) l2cap_clear_timer(c, &c->ack_timer)
>   
>   static inline int __seq_offset(struct l2cap_chan *chan, __u16 seq1, __u16 seq2)

Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>


Kind regards,

Paul

      parent reply	other threads:[~2026-08-29 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-29 15:13 [PATCH] Bluetooth: L2CAP: fix wrong identifier in __set_ack_timer() Pauli Virtanen
2026-08-29 15:47 ` bluez.test.bot
2026-08-29 23:24 ` Paul Menzel [this message]

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=e4f4931b-c930-4efd-9bbb-9f83d6ddf360@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pav@iki.fi \
    /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