linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: [PATCH BlueZ] mesh: Send correct NetKey index in DevKeyMessageReceived
Date: Thu, 20 Aug 2020 14:29:18 +0000	[thread overview]
Message-ID: <01cbff2b3bc7d6c7b97e75fa93e6444480fbf262.camel@intel.com> (raw)
In-Reply-To: <20200819214802.83756-1-inga.stotland@intel.com>

Applied
On Wed, 2020-08-19 at 14:48 -0700, Inga Stotland wrote:
> The value of net_index in DevKeyMessageReceived() method must be set
> to the value of a subnet index on which a device key encoded message
> has been received. Was hard coded to 0. Fixed.
> ---
>  mesh/model.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mesh/model.c b/mesh/model.c
> index b44e2f669..9529dfb2e 100644
> --- a/mesh/model.c
> +++ b/mesh/model.c
> @@ -965,7 +965,8 @@ bool mesh_model_rx(struct mesh_node *node, bool szmict, uint32_t seq0,
>  			else if (decrypt_idx == APP_IDX_DEV_REMOTE ||
>  				 decrypt_idx == APP_IDX_DEV_LOCAL)
>  				send_dev_key_msg_rcvd(node, i, src, decrypt_idx,
> -						0, forward.size, forward.data);
> +							net_idx, forward.size,
> +								forward.data);
>  		}
>  
>  		/*

      reply	other threads:[~2020-08-20 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 21:48 [PATCH BlueZ] mesh: Send correct NetKey index in DevKeyMessageReceived Inga Stotland
2020-08-20 14:29 ` Gix, Brian [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=01cbff2b3bc7d6c7b97e75fa93e6444480fbf262.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.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 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).