From: Darren Hart <dvhart@infradead.org>
To: Azael Avalos <coproscefalo@gmail.com>
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] toshiba_acpi: Remove bluetooth rfkill code
Date: Sun, 3 May 2015 12:19:55 -0700 [thread overview]
Message-ID: <20150503191955.GC16105@fury.dvhart.com> (raw)
In-Reply-To: <1430166654-15010-2-git-send-email-coproscefalo@gmail.com>
On Mon, Apr 27, 2015 at 02:30:53PM -0600, Azael Avalos wrote:
> This patch removes all bluetooth rfkill related code residing in
> the toshiba_acpi driver.
>
> Separate patches will add (and adapt) the code to toshiba_bluetooth
> (where it belongs).
>
> Signed-off-by: Azael Avalos <coproscefalo@gmail.com>
Hi Azael,
With this applied the driver as build warnings:
...
CC [M] drivers/platform/x86/toshiba_acpi.o
drivers/platform/x86/toshiba_acpi.c: In function ‘toshiba_acpi_add’:
drivers/platform/x86/toshiba_acpi.c:2636:7: warning: unused variable ‘bt_present’ [-Wunused-variable]
bool bt_present;
^
drivers/platform/x86/toshiba_acpi.c: At top level:
drivers/platform/x86/toshiba_acpi.c:358:12: warning: ‘hci_write2’ defined but not used [-Wunused-function]
static u32 hci_write2(struct toshiba_acpi_dev *dev, u32 reg, u32 in1, u32 in2)
I presume these should be removed as well?
Thanks,
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-05-03 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 20:30 [PATCH 0/2] toshiba_acpi: Purge driver from bluetooth RFKill code Azael Avalos
2015-04-27 20:30 ` [PATCH 1/2] toshiba_acpi: Remove bluetooth rfkill code Azael Avalos
2015-05-03 19:19 ` Darren Hart [this message]
2015-04-27 20:30 ` [PATCH 2/2] platform/x86: Remove RFKILL dependency from toshiba_acpi Azael Avalos
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=20150503191955.GC16105@fury.dvhart.com \
--to=dvhart@infradead.org \
--cc=coproscefalo@gmail.com \
--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®