Linux bluetooth development
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org
Subject: Re: pull request: bluetooth 2024-12-11
Date: Thu, 12 Dec 2024 13:20:34 +0100	[thread overview]
Message-ID: <b6ebd1f0-d914-4044-913b-621071a1b123@redhat.com> (raw)
In-Reply-To: <ba32a8c5-3d90-437e-a4bc-a67304230f79@redhat.com>



On 12/12/24 12:55, Paolo Abeni wrote:
> On 12/11/24 18:21, Luiz Augusto von Dentz wrote:
>> The following changes since commit 3dd002f20098b9569f8fd7f8703f364571e2e975:
>>
>>   net: renesas: rswitch: handle stop vs interrupt race (2024-12-10 19:08:00 -0800)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth.git tags/for-net-2024-12-11
>>
>> for you to fetch changes up to 69e8a8410d7bcd3636091b5915a939b9972f99f1:
>>
>>   Bluetooth: btmtk: avoid UAF in btmtk_process_coredump (2024-12-11 12:01:13 -0500)
> 
> On top of this I see a new build warning:
> 
> net/bluetooth/hci_core.c:60:1: warning: symbol 'hci_cb_list_lock' was
> not declared. Should it be static?
> 
> Would you mind fixing that and re-sending? We are still on time for
> tomorrow 'net' PR.

Whoops, I lost track of current time, the net PR will be later today
(sorry for the confusion!), but there is stills some time for the update.

/P


  reply	other threads:[~2024-12-12 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 17:21 pull request: bluetooth 2024-12-11 Luiz Augusto von Dentz
2024-12-12 11:55 ` Paolo Abeni
2024-12-12 12:20   ` Paolo Abeni [this message]
2024-12-12 14:22     ` Luiz Augusto von Dentz

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=b6ebd1f0-d914-4044-913b-621071a1b123@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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