From: Szymon Janc <szymon.janc@codecoup.pl>
To: "Łukasz Rymanowski" <lukasz.rymanowski@codecoup.pl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/5] monitor: Add description for filter in scan parameters
Date: Wed, 19 Apr 2017 16:12:26 +0200 [thread overview]
Message-ID: <2270039.JPxRPnK7gO@ix> (raw)
In-Reply-To: <20170412124127.31486-1-lukasz.rymanowski@codecoup.pl>
Hi =C5=81ukasz,
On Wednesday, 12 April 2017 14:41:23 CEST =C5=81ukasz Rymanowski wrote:
> < HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7
> Type: Active (0x01)
> Interval: 30.000 msec (0x0030)
> Window: 30.000 msec (0x0030)
> Own address type: Public (0x00)
> Filter policy: Accept all advertisement, inc. directed unresolved
> RPA (0x02) ---
> monitor/packet.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>=20
> diff --git a/monitor/packet.c b/monitor/packet.c
> index 5d927f5..219542e 100644
> --- a/monitor/packet.c
> +++ b/monitor/packet.c
> @@ -6309,6 +6309,12 @@ static void le_set_scan_parameters_cmd(const void
> *data, uint8_t size) case 0x01:
> str =3D "Ignore not in white list";
> break;
> + case 0x02:
> + str =3D "Accept all advertisement, inc. directed unresolved RPA";
> + break;
> + case 0x03:
> + str =3D "Ignore not in white list, exc. directed unresolved RPA";
> + break;
> default:
> str =3D "Reserved";
> break;
All patches applied, thanks.
=2D-=20
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2017-04-19 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 12:41 [PATCH BlueZ v2 1/5] monitor: Add description for filter in scan parameters Łukasz Rymanowski
2017-04-12 12:41 ` [PATCH BlueZ v2 2/5] monitor: Add LE Read PHY decoding Łukasz Rymanowski
2017-04-12 12:41 ` [PATCH BlueZ v2 3/5] monitor: Add LE Set default " Łukasz Rymanowski
2017-04-12 12:41 ` [PATCH BlueZ v2 4/5] monitor: Add LE Set " Łukasz Rymanowski
2017-04-12 12:41 ` [PATCH BlueZ v2 5/5] monitor: Add LE PHY update complete event decoding Łukasz Rymanowski
2017-04-19 14:12 ` Szymon Janc [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=2270039.JPxRPnK7gO@ix \
--to=szymon.janc@codecoup.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lukasz.rymanowski@codecoup.pl \
/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;
as well as URLs for NNTP newsgroup(s).