From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 206815] bluez-5.53: unit/test-mesh-crypto fails
Date: Wed, 11 Mar 2020 20:50:37 +0000 [thread overview]
Message-ID: <bug-206815-62941-VmoCz3qGfV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206815-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206815
--- Comment #3 from Brian Gix (brian.gix@gmail.com) ---
With some notable exceptions (Raspbian) most workstation and laptop distros
already support all of the needed CRYPTO_USER_* dependancies... But I will add
the known list to the bluez README file.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-03-11 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 13:16 [Bug 206815] New: bluez-5.53: unit/test-mesh-crypto fails bugzilla-daemon
2020-03-11 20:50 ` bugzilla-daemon [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=bug-206815-62941-VmoCz3qGfV@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 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.