public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 string of public-oob and static-oob
Date: Tue, 3 Dec 2019 18:49:59 +0000	[thread overview]
Message-ID: <4edddf7f571f90c0ea8b0cb072dea166690d470e.camel@intel.com> (raw)
In-Reply-To: <1575367285-8098-1-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>
> 
> Fix string typo as per mesh-api.txt
> ---
>  mesh/agent.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mesh/agent.c b/mesh/agent.c
> index 5a5570a..9f9399f 100644
> --- a/mesh/agent.c
> +++ b/mesh/agent.c
> @@ -131,9 +131,9 @@ static void parse_prov_caps(struct mesh_agent_prov_caps *caps,
>  			break;
>  		}
>  
> -		if (!strcmp(str, "PublicOOB"))
> +		if (!strcmp(str, "public-oob"))
>  			caps->pub_type = 1;
> -		else if (!strcmp(str, "StaticOOB"))
> +		else if (!strcmp(str, "static-oob"))
>  			caps->static_type = 1;
>  	}
>  

      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
2019-12-03 10:01   ` [PATCH 1/1] mesh: Fix to send close indication on timeout Prathyusha Nelluri
2019-12-03 18:49   ` 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=4edddf7f571f90c0ea8b0cb072dea166690d470e.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