From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] PATCH:
Date: Sun, 04 Nov 2007 13:21:50 +0000 [thread overview]
Message-ID: <472DC76E.2070200@hhs.nl> (raw)
In-Reply-To: <46F3DD44.4070307@hhs.nl>
Jean Delvare wrote:
> Hi Hans,
>
> On Fri, 02 Nov 2007 20:41:19 +0100, Hans de Goede wrote:
>> Jean Delvare wrote:
>>> On Fri, 02 Nov 2007 08:35:53 +0100, Hans de Goede wrote:
>>>> Good work Jean, yes that should do the job, I stared myself blind at adding a
>>>> clean way to store the data for later retrieval to the existing __init parser,
>>>> your way indeed will work and is much more generic.
>>>>
>>>> I'll compile a kernel with the dmi_scan.c and dmi.h parts patched in and then
>>>> start working on integrating this into fschmd.c
>>> Here's an updated version of my patch, with no code duplication this
>>> time. This should be easier to get this accepted upstream. To make the
>>> code even smaller, dmi_table() could be merged into dmi_present() but
>>> that's about it.
>> Looks good, I found inconsistency though, in essence the dmi_table() and
>> dmi_walk() are the same, (except for dmi_ioremap versus ioremap ofcourse) but
>> for one you just use the base, len and number of items stored in global
>> variables, while for the other you pass those same global variables through
>> parameters, for consistency sake I think you should to both the same.
>
> That's an asymmetry rather than an inconsistency. There are two reasons
> for it, firstly I avoid using global variables when I don't have to,
> secondly this happened to make the patch smaller. It is of course
> possible to use the global variables dmi_base, dmi_len and dmi_num in
> dmi_table() rather than passing them as parameters; doing so makes the
> binary code slightly smaller. I'm attaching a version of the patch that
> does this, together with function renames to make it look better. If
> you like this one, I could send it upstream for review and comments.
>
I like this one, you may want to wait with sending it upstream till I've
actually tested if it solves the problem at hand though.
I'm currently rather busy at work, so this may take a week or so.
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-11-04 13:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 15:03 [lm-sensors] PATCH: Hans de Goede
2007-09-24 14:28 ` Jean Delvare
2007-10-07 8:19 ` Jean Delvare
2007-10-07 11:37 ` Hans de Goede
2007-10-07 18:24 ` Mark M. Hoffman
2007-10-07 18:28 ` Mark M. Hoffman
2007-10-07 20:41 ` Jean Delvare
2007-10-07 22:05 ` Jean Delvare
2007-10-31 8:42 ` Hans de Goede
2007-10-31 15:17 ` Jean Delvare
2007-11-01 23:00 ` Jean Delvare
2007-11-02 7:35 ` Hans de Goede
2007-11-02 9:44 ` Jean Delvare
2007-11-02 19:41 ` Hans de Goede
2007-11-03 16:29 ` Jean Delvare
2007-11-04 13:21 ` Hans de Goede [this message]
2007-12-17 15:56 ` Hans de Goede
2007-12-18 13:29 ` Jean Delvare
2008-06-30 14:53 ` Hans de Goede
2009-01-30 10:29 ` Hans de Goede
2009-01-30 11:06 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 12:35 [lm-sensors] Patch: Jean Delvare
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=472DC76E.2070200@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=lm-sensors@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 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.