From: iwestin <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] be7ebf: mesh: Use correct net_id for received CTL messages
Date: Thu, 30 Jun 2022 13:22:00 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/1d6cfb-be7ebf@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: be7ebf29b370d298290f6a4eceb31b1d9c94081c
https://github.com/bluez/bluez/commit/be7ebf29b370d298290f6a4eceb31b1d9c94081c
Author: Isak Westin <isak.westin@hotmail.com>
Date: 2022-06-30 (Thu, 30 Jun 2022)
Changed paths:
M mesh/net.c
Log Message:
-----------
mesh: Use correct net_id for received CTL messages
For received CTL mesh messages, the wrong network ID variable was
passed to ctl_received. This patch changes to the correct variable.
Also, changed type of net_key_id argument in ctl_received function
to be consistent wich the whole call chain.
reply other threads:[~2022-06-30 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/1d6cfb-be7ebf@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@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 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.