All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 196621] bluez-5.46: unit/test-gatt segfaults when running tests
Date: Wed, 11 Mar 2020 12:14:21 +0000	[thread overview]
Message-ID: <bug-196621-62941-aojY2qollm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196621-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=196621

--- Comment #7 from Pacho Ramos (pachoramos1@gmail.com) ---
(In reply to Pacho Ramos from comment #6)
> It seems that CONFIG_CRYPTO_USER_API_HASH is the only needed (at least with
> 5.50)

is that really needed only for tests or for general USE? To know if I need to
enforce that option for regular users or only for those wanting to run tests.

Thanks a lot for the info

-- 
You are receiving this mail because:
You are the assignee for the bug.

       reply	other threads:[~2020-03-11 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-196621-62941@https.bugzilla.kernel.org/>
2020-03-11 12:14 ` bugzilla-daemon [this message]
2020-03-11 12:18 ` [Bug 196621] bluez-5.46: unit/test-gatt segfaults when running tests bugzilla-daemon

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-196621-62941-aojY2qollm@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.