From: "Pali Rohár" <pali.rohar@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Darren Hart <dvhart@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
lkml <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: dell_rbtn - kernel panic at boot...
Date: Mon, 25 May 2015 08:03:42 +0200 [thread overview]
Message-ID: <201505250803.42410@pali> (raw)
In-Reply-To: <20150525050121.GA28810@srcf.ucam.org>
[-- Attachment #1: Type: Text/Plain, Size: 743 bytes --]
On Monday 25 May 2015 07:01:21 Matthew Garrett wrote:
> On Sun, May 24, 2015 at 09:44:32PM -0700, Darren Hart wrote:
> > Greg, Matthew, I'm tempted to recommend this 434 line driver be
> > rolled into dell-laptop.c. Any strong opinions?
>
> Mrm. It's slightly conceptually nasty in that one's an ACPI driver
> and one's calling a Dell custom interface, but I think merging them
> is probably the last bad answer.
I think merging does not fix our problem. dell laptop rfkill driver
needs to be initialized after dell-rbtn acpi driver register itself.
And dell-laptop and dell-rbtn are two different devices (one dell smbios
and one acpi) and it for me it sounds like bad idea too...
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-05-25 6:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 2:06 dell_rbtn - kernel panic at boot Valdis Kletnieks
2015-05-22 22:53 ` Dmitry Torokhov
2015-05-23 1:05 ` Pali Rohár
2015-05-23 20:08 ` Pali Rohár
2015-05-25 4:44 ` Darren Hart
2015-05-25 5:01 ` Matthew Garrett
2015-05-25 6:03 ` Pali Rohár [this message]
2015-05-27 4:16 ` Darren Hart
2015-05-27 7:28 ` Pali Rohár
2015-05-29 3:15 ` Darren Hart
2015-05-25 14:40 ` Pali Rohár
2015-05-27 4:09 ` Darren Hart
2015-05-27 4:24 ` 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=201505250803.42410@pali \
--to=pali.rohar@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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