From: "Gix, Brian" <brian.gix@intel.com>
To: "prathyusha.n@samsung.com" <prathyusha.n@samsung.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/1] mesh: Fix invalid transaction number in PROV_INVITE
Date: Tue, 3 Dec 2019 18:50:15 +0000 [thread overview]
Message-ID: <d806af62b13b384ed003a38ed92c3ae95398a9e4.camel@intel.com> (raw)
In-Reply-To: <1575367285-8098-2-git-send-email-prathyusha.n@samsung.com>
Applied
On Tue, 2019-12-03 at 15:31 +0530, Prathyusha Nelluri wrote:
> From: Prathyusha N <prathyusha.n@samsung.com>
>
> For initiator, transaction number starts from 0x00 where as for acceptor
> transaction number starts from 0x80. Since transaction number is
> pre-incremented and sent in every packet, initialize it with 0xFF for
> initiator and 0x7F for acceptor.
> ---
> mesh/pb-adv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mesh/pb-adv.c b/mesh/pb-adv.c
> index 6b4a700..19d1453 100644
> --- a/mesh/pb-adv.c
> +++ b/mesh/pb-adv.c
> @@ -292,6 +292,7 @@ static void pb_adv_packet(void *user_data, const uint8_t *pkt, uint16_t len)
> /* Only call Open callback once */
> if (first) {
> l_debug("PB-ADV open confirmed");
> + session->local_trans_num = 0xFF;
> session->open_cb(session->user_data, pb_adv_tx,
> session, PB_ADV);
> }
next prev parent reply other threads:[~2019-12-03 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191203100133epcas5p1bf4b021f6cabcba3b5ff67965ccfec56@epcas5p1.samsung.com>
2019-12-03 10:01 ` [PATCH 1/1] mesh: Fix string of public-oob and static-oob Prathyusha Nelluri
2019-12-03 10:01 ` [PATCH 1/1] mesh: Fix invalid transaction number in PROV_INVITE Prathyusha Nelluri
2019-12-03 18:50 ` Gix, Brian [this message]
2019-12-03 10:01 ` [PATCH 1/1] mesh: Fix to send close indication on timeout Prathyusha Nelluri
2019-12-03 18:49 ` [PATCH 1/1] mesh: Fix string of public-oob and static-oob Gix, Brian
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=d806af62b13b384ed003a38ed92c3ae95398a9e4.camel@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=prathyusha.n@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox