From: patchwork-bot+bluetooth@kernel.org
To: Prathibha Madugonde <quic_prathm@quicinc.com>
Cc: linux-bluetooth@vger.kernel.org, pmenzel@molgen.mpg.de,
luiz.dentz@gmail.com, quic_mohamull@quicinc.com,
quic_hbandi@quicinc.com, quic_anubhavg@quicinc.com
Subject: Re: [PATCH BlueZ] Set BREDR not supported bit in AD Flag when discoverable is off
Date: Mon, 08 Jul 2024 16:00:30 +0000 [thread overview]
Message-ID: <172045443014.21290.6030624814065789158.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240708074454.5891-1-quic_prathm@quicinc.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 8 Jul 2024 13:14:54 +0530 you wrote:
> From: Prathibha Madugonde <quic_prathm@quicinc.com>
>
> Fix for GAP/DISC/NONM/BV-02-C
> As per GAP.TS.p44 test spec
> IUT does not contain General Discoverable mode and Limited Discoverable
> mode in the AD Type Flag. IUT shall send AD Type Flag to PASS the test
> case, thus set BR/EDR not supported bit in the AD Type Flag when
> discoverable is off.
>
> [...]
Here is the summary with links:
- [BlueZ] Set BREDR not supported bit in AD Flag when discoverable is off
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=42d43b28428f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-07-08 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 7:44 [PATCH BlueZ] Set BREDR not supported bit in AD Flag when discoverable is off quic_prathm
2024-07-08 9:44 ` [BlueZ] " bluez.test.bot
2024-07-08 16:00 ` patchwork-bot+bluetooth [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 7:37 [PATCH BlueZ] " quic_prathm
2024-07-05 17:20 ` Luiz Augusto von Dentz
2024-07-05 5:37 quic_prathm
2024-07-03 9:05 quic_prathm
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=172045443014.21290.6030624814065789158.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=quic_prathm@quicinc.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.