Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Alain Michaud <alainmichaud@google.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Alain Michaud <alainm@chromium.org>,
	BlueZ <linux-bluetooth@vger.kernel.org>
Subject: Re: [Bluez PATCH] doc: Add definition for Set Kernel Debug Level
Date: Tue, 21 Jan 2020 20:33:28 +0200	[thread overview]
Message-ID: <D0C01568-E48B-46ED-A2CC-D19FB2895756@gmail.com> (raw)
In-Reply-To: <CALWDO_WyZUvkOgXVSd12q7Trg_=LqSb9KQsXH9_C_k8_kD0ddQ@mail.gmail.com>

Hi Alain,

On 21. Jan 2020, at 20.25, Alain Michaud <alainmichaud@google.com> wrote:
> I'm not familiar with the dynamic_debug feature.
> 
> On ChromiumOS, the interface proposed here is used by the user
> feedback system to allow the collection of BT_DBG output when the user
> is trying to send us feedback.  If there is a better way to do this,
> we can certainly use that. but may need to be pointed in the right
> direction.

I think Marcel is referring to this:

https://www.kernel.org/doc/html/latest/admin-guide/dynamic-debug-howto.html

Johan

  reply	other threads:[~2020-01-21 18:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 20:27 [Bluez PATCH] doc: Add definition for Set Kernel Debug Level Alain Michaud
2020-01-21 16:20 ` Marcel Holtmann
2020-01-21 18:25   ` Alain Michaud
2020-01-21 18:33     ` Johan Hedberg [this message]
2020-01-21 18:37       ` Alain Michaud
2020-01-22 21:48         ` Alain Michaud
2020-01-23  5:52           ` Marcel Holtmann
2020-01-23 14:38             ` Alain Michaud
2020-01-23 17:44               ` Marcel Holtmann
2020-01-23 18:04                 ` Alain Michaud
2020-01-23 18:16                   ` Marcel Holtmann
2020-01-23 18:18                     ` Alain Michaud
2020-01-23 23:13                       ` Luiz Augusto von Dentz
2020-01-27 16:54                     ` Marcel Holtmann

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=D0C01568-E48B-46ED-A2CC-D19FB2895756@gmail.com \
    --to=johan.hedberg@gmail.com \
    --cc=alainm@chromium.org \
    --cc=alainmichaud@google.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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