linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael N. Moran" <mike@mnmoran.org>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: [PATCH BlueZ v2 0/1] mesh: Add strings for SIG Model IDs
Date: Mon, 3 Aug 2020 10:06:51 -0400	[thread overview]
Message-ID: <ede1e2f7-e6eb-f878-6bd4-f540200da198@mnmoran.org> (raw)

My first BlueZ patch.

This patch adds a utility function returning a string
describing a SIG Model ID and uses this function
for in the mesh-cfgclient in the list-nodes command
output and in the display of received composition data.

The strings were taken directly from the Bluetooth Mesh Profile
and Mesh Model specifications.

Fixed style issues.

Michael N. Moran (1):
   Add strings for SIG Model IDs

  tools/mesh/cfgcli.c |  3 ++-
  tools/mesh/remote.c |  5 ++--
  tools/mesh/util.c   | 64 
+++++++++++++++++++++++++++++++++++++++++++++
  tools/mesh/util.h   |  1 +
  4 files changed, 70 insertions(+), 3 deletions(-)

-- 
2.26.2


                 reply	other threads:[~2020-08-03 14:06 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=ede1e2f7-e6eb-f878-6bd4-f540200da198@mnmoran.org \
    --to=mike@mnmoran.org \
    --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).