From: inga-s <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e71e11: mesh: Fix mesh to work with MESH_IO_TYPE_UNIT_TEST
Date: Wed, 05 Oct 2022 14:18:44 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/fe9427-e71e11@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e71e1103abc63df5ba445897036eabfda4de2a2d
https://github.com/bluez/bluez/commit/e71e1103abc63df5ba445897036eabfda4de2a2d
Author: Inga Stotland <inga.stotland@intel.com>
Date: 2022-10-05 (Wed, 05 Oct 2022)
Changed paths:
M mesh/main.c
M mesh/mesh-io.c
Log Message:
-----------
mesh: Fix mesh to work with MESH_IO_TYPE_UNIT_TEST
This fixes mesh io flow for MESH_IO_TYPE_UNIT_TEST which
got broken after:
commit 9966cb8b6999a5f54fc13acbd7e1526512a84342
("mesh: Add new kernel MGMT based IO transport")
reply other threads:[~2022-10-05 21:18 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/fe9427-e71e11@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.