All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Bluetooth: SCO: Use kref to track lifetime of sco_conn
Date: Mon, 11 Nov 2024 16:10:31 +0000	[thread overview]
Message-ID: <173134143176.4081786.18186640433728678880.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241107183455.129897-1-luiz.dentz@gmail.com>

Hello:

This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  7 Nov 2024 13:34:54 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> 
> This make use of kref to keep track of reference of sco_conn which
> allows better tracking of its lifetime with usage of things like
> kref_get_unless_zero in a similar way as used in l2cap_chan.
> 
> In addition to it remove call to sco_sock_set_timer on __sco_sock_close
> since at that point it is useless to set a timer as the sk will be freed
> there is nothing to be done in sco_sock_timeout.
> 
> [...]

Here is the summary with links:
  - [v1,1/2] Bluetooth: SCO: Use kref to track lifetime of sco_conn
    https://git.kernel.org/bluetooth/bluetooth-next/c/c5438f5c915a
  - [v1,2/2] Bluetooth: ISO: Use kref to track lifetime of iso_conn
    https://git.kernel.org/bluetooth/bluetooth-next/c/607ef969e6eb

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



      parent reply	other threads:[~2024-11-11 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 18:34 [PATCH v1 1/2] Bluetooth: SCO: Use kref to track lifetime of sco_conn Luiz Augusto von Dentz
2024-11-07 18:34 ` [PATCH v1 2/2] Bluetooth: ISO: Use kref to track lifetime of iso_conn Luiz Augusto von Dentz
2024-11-11 16:10 ` patchwork-bot+bluetooth [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=173134143176.4081786.18186640433728678880.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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 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.