From: Andrey Panin <pazke@donpac.ru>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC] DMI cleanup patches
Date: Thu, 6 May 2004 14:29:04 +0400 [thread overview]
Message-ID: <20040506102904.GA3295@pazke> (raw)
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
Hi all,
currently arch/i386/kernel/dmi_scan.c file looks like complete
mess. Interfacing with other kernel subsystem made using
ad-hoc ways, mostly with ugly global variables, additionaly
coding style is ... not good. So these patches appear:
patch-dmi-1-matches - simplify DMI blacklist table by
removing the need to fill unused slots with NO_MATCH macro.
patch-dmi-2-api - separate and export dmi_check_system()
function (along with some needed declarations) which checks given
DMI id table against system DMI data and runs callback functions
when necessary.
patch-dmi-3-whitespace - various coding style cleanups.
patch-dmi-4-sonypi - make sonypi driver use dmi_check_system()
function and remove is_sony_vaio_laptop global variable.
patch-dmi-5-apm - make APM BIOS driver use dmi_check_system()
function and move all related quirks into apm.c.
patch-dmi-6-pciirq - make pci irq routing code use
dmi_check_system() function and make broken_hp_bios_irq9 variable
static.
patch-dmi-7-smbus - make PIIX4 I2C use dmi_check_system()
function and remove is_unsafe_smbus global variable.
Please take a look.
Best regards.
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-05-06 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 10:29 Andrey Panin [this message]
2004-05-06 11:47 ` [RFC] DMI cleanup patches Dave Jones
2004-05-06 14:39 ` Linus Torvalds
2004-05-06 15:10 ` Andrew Morton
2004-05-06 16:32 ` Dave Jones
2004-05-06 21:23 ` Andrew Morton
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=20040506102904.GA3295@pazke \
--to=pazke@donpac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.