From: Prathyusha Nelluri <prathyusha.n@samsung.com>
To: linux-bluetooth@vger.kernel.org
Cc: Prathyusha N <prathyusha.n@samsung.com>
Subject: [PATCH 1/1] mesh: Fix string of public-oob and static-oob
Date: Tue, 3 Dec 2019 15:31:23 +0530 [thread overview]
Message-ID: <1575367285-8098-1-git-send-email-prathyusha.n@samsung.com> (raw)
In-Reply-To: CGME20191203100133epcas5p1bf4b021f6cabcba3b5ff67965ccfec56@epcas5p1.samsung.com
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;
}
--
2.7.4
next parent reply other threads:[~2019-12-03 10:01 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 ` Prathyusha Nelluri [this message]
[not found] ` <CGME20191203100133epcas5p190c7b3e7e06d84b1db57ec85054876ef@epcas5p1.samsung.com>
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
[not found] ` <CGME20191203100134epcas5p4855ab386bd90877c85114b970a252223@epcas5p4.samsung.com>
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=1575367285-8098-1-git-send-email-prathyusha.n@samsung.com \
--to=prathyusha.n@samsung.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).