From: "Bjørn Mork" <bjorn@mork.no>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
"platform-driver-x86\@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/6] toshiba_bluetooth: Change BT status message to debug
Date: Tue, 28 Apr 2015 17:16:19 +0200 [thread overview]
Message-ID: <87zj5sgu64.fsf@nemi.mork.no> (raw)
In-Reply-To: <CAGdLNWGJger9MRmd0NQaooiuMPjGJA1rG+xGSJWtF84UEU+CFQ@mail.gmail.com> (Azael Avalos's message of "Tue, 28 Apr 2015 09:08:32 -0600")
Azael Avalos <coproscefalo@gmail.com> writes:
> Well, I was under the impression that what really gets printed is:
> toshiba_bluetooth: killswitch 1
Ah, right. Yes, I missed the
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
you already had in the module. That helps a lot.
Bjørn
next prev parent reply other threads:[~2015-04-28 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 20:32 [PATCH 0/6] toshiba_bluetooth: Add rfkill code to driver Azael Avalos
2015-04-27 20:32 ` [PATCH 1/6] toshiba_bluetooth: Add a container struct named toshiba_bluetooth_dev Azael Avalos
2015-04-27 20:32 ` [PATCH 2/6] toshiba_bluetooth: Add RFKill handler functions Azael Avalos
2015-04-27 20:32 ` [PATCH 3/6] toshiba_bluetooth: Clean toshiba_bluetooth_enable function Azael Avalos
2015-05-03 19:43 ` Darren Hart
2015-04-27 20:32 ` [PATCH 4/6] toshiba_bluetooth: Adapt *_notify and *_resume functions to rfkill Azael Avalos
2015-04-27 20:32 ` [PATCH 5/6] toshiba_bluetooth: Change BT status message to debug Azael Avalos
2015-04-28 7:36 ` Bjørn Mork
2015-04-28 15:08 ` Azael Avalos
2015-04-28 15:16 ` Bjørn Mork [this message]
2015-05-03 19:49 ` Darren Hart
2015-04-27 20:32 ` [PATCH 6/6] platform/x86: Add RFKILL dependency to toshiba_bluetooth driver Azael Avalos
2015-05-03 19:47 ` Darren Hart
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=87zj5sgu64.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=coproscefalo@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®