linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tedd An <tedd.an@linux.intel.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC v3] Bluetooth: Add debugfs option to enable runtime debug statements
Date: Thu, 13 Feb 2020 09:33:47 -0800	[thread overview]
Message-ID: <A923F940-6CAA-4D31-AAEF-28F5A2312676@linux.intel.com> (raw)
In-Reply-To: <AF6B4197-8AFE-429A-ACFB-14500A7D500F@holtmann.org>

Hi Marcel,
    
I have some cycle today and tomorrow and I can run quick test.
Is there any procedure you want me to test other than enabling kernel config and enable via debugfs?
Let me know.
    
Regards,
Tedd

On 2/12/20, 11:31 PM, "Marcel Holtmann" <linux-bluetooth-owner@vger.kernel.org on behalf of marcel@holtmann.org> wrote:

    Hi,
    
    > Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
    > ---
    > include/net/bluetooth/bluetooth.h | 10 +++++
    > net/bluetooth/Kconfig             |  7 +++
    > net/bluetooth/af_bluetooth.c      |  2 +
    > net/bluetooth/lib.c               | 73 +++++++++++++++++++++++++++++++
    > 4 files changed, 92 insertions(+)
    
    does anybody have any comments on this. It is not the final solution, but as an interim it might be a good start.
    
    I have not seen any kbuild issues popping up. However I like to get some Tested-By, Reviewed-By lines added to the patch and I can send a patch version with proper commit message if there is interest in getting this upstream.
    
    Regards
    
    Marcel
    
    



  reply	other threads:[~2020-02-13 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 15:36 [RFC v3] Bluetooth: Add debugfs option to enable runtime debug statements Marcel Holtmann
2020-02-13  7:27 ` Marcel Holtmann
2020-02-13 17:33   ` Tedd An [this message]
2020-02-13 23:03   ` Tedd Ho-Jeong An

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=A923F940-6CAA-4D31-AAEF-28F5A2312676@linux.intel.com \
    --to=tedd.an@linux.intel.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;
as well as URLs for NNTP newsgroup(s).