From: Pavel Machek <pavel@ucw.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Alexandre Rostovtsev <tetromino@gmail.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lenovo-sl-laptop : driver for review
Date: Tue, 10 Mar 2009 12:22:09 +0100 [thread overview]
Message-ID: <20090310112209.GB1337@ucw.cz> (raw)
In-Reply-To: <20090228143711.GB17541@khazad-dum.debian.net>
On Sat 2009-02-28 11:37:11, Henrique de Moraes Holschuh wrote:
> On Fri, 27 Feb 2009, Pavel Machek wrote:
> > > +module_param(debug_ec, bool, S_IRUGO);
> > > +MODULE_PARM_DESC(debug_ec,
> > > + "Present EC debugging interface in procfs. WARNING: writing to the "
> > > + "EC can hang your system and possibly damage your hardware.");
> >
> > Sounds dangerous and clearly does not belong to /proc. Please drop it.
>
> ThinkPad ACPI also has one. OTOH, we are fairly sure one cannot damage the
> standard ThinkPad hardware through the "IBM thinkpad-style" EC firmware, the
> EC sanity-checks things. I suppose you could cause the box to go away for
> lunch and don't come back until a complete hardware reset, or hit one of the
> crash-the-EC-firmware bugs by accident, though.
Yeah but that interface still does not belong to /proc. Please drop it
from merge version at least.
> > > +/*************************************************************************
> > > + bluetooth sysfs - copied nearly verbatim from thinkpad_acpi.c
> > > + *************************************************************************/
> >
> > That's quite a lot of code for verbatim copy; create shared helper?
>
> Yeah, I am game. But let's do it later on and not delay anything because of
> it, please. I will start breaking thinkpad-acpi into multiple source files,
> and after that is done (should take a while, thinkpad-acpi is a big module
> with a LOT of subdriver interdependencies) we can look for the best way to
> reduce code duplication.
Well, this monolith is quite long/hard to review. IMO it should be
split to make review easy.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-03-10 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 7:59 [PATCH] lenovo-sl-laptop : driver for review Alexandre Rostovtsev
2009-02-16 15:18 ` Matthew Garrett
2009-02-20 3:00 ` Henrique de Moraes Holschuh
2009-02-16 15:21 ` Matthew Garrett
2009-02-27 13:27 ` Pavel Machek
2009-02-28 14:37 ` Henrique de Moraes Holschuh
2009-03-10 11:22 ` Pavel Machek [this message]
2009-03-10 11:34 ` Henrique de Moraes Holschuh
2009-03-10 14:12 ` Pavel Machek
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=20090310112209.GB1337@ucw.cz \
--to=pavel@ucw.cz \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tetromino@gmail.com \
/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