From: Goffredo Baroncelli <kreijack@gmail.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, bryan@whatroute.net,
Goffredo Baroncelli <kreijack@inwind.it>
Subject: Re: [PATCH 3/4] Add the "verbose" module option.
Date: Sun, 03 Aug 2014 17:12:57 +0200 [thread overview]
Message-ID: <53DE5179.3080402@gmail.com> (raw)
In-Reply-To: <20140803161223.0b26e4bc@endymion.delvare>
On 08/03/2014 04:12 PM, Jean Delvare wrote:
> Hi Goffredo,
>
> You messed up your Cc's ;-)
I fight hard with git-send-email.... In the next trip I will check two times !
>
> On Fri, 1 Aug 2014 14:00:49 +0000, Goffredo Baroncelli wrote:
>> The "verbose" option controls the message in the kernel log
>> verbose = 0 no message
>> verbose = 1 log only the fan speed changes
>> verbose = 2 log the fan speed changes and the temperature changes
>>
>> Signed-off-by: Goffredo Baroncelli <kreijack@inwind.it>
>> ---
>> drivers/macintosh/therm_windtunnel.c | 37 +++++++++++++++++++++++-------------
>> 1 file changed, 24 insertions(+), 13 deletions(-)
>>
>> diff --git a/drivers/macintosh/therm_windtunnel.c b/drivers/macintosh/therm_windtunnel.c
>> index 1e50455..0c4eb85 100644
>> --- a/drivers/macintosh/therm_windtunnel.c
>> +++ b/drivers/macintosh/therm_windtunnel.c
>> @@ -44,7 +44,11 @@
>> #include <asm/sections.h>
>> #include <asm/macio.h>
>>
>> -#define LOG_TEMP 0 /* continuously log temperature */
>> +static int verbose = 1; /* see description below */
>
> This comment seems useless.
ok
>
>> +module_param(verbose, int, 0644);
>> +MODULE_PARM_DESC(verbose, "Vebosity level: 0=silent, "
>
> Typo: Verbosity
Ok
>
>> + "1=log the fan tuning, "
>> + "2=log the temperature.");
>
> Trailing dot is not needed.
OK
>>
>> static struct {
[... cut cut cut ...]
>> + /*
>> + * if verbose >0 log each fan tuning
>> + * if verbose >1 log each cpu temperature change
>> + */
>
> I think it is a good idea to have all the printing in a single place.
>
>> + if ((verbose > 1 && x.temp != temp ) ||
>
> No space before closing parenthesis. I know the original code did not
> follow the standard coding style but you have the opportunity to make
> it better. Same many times below. scripts/checkpatch.pl tells you about
> that and many other style issues, most of which are easily fixable.
>
> Also don't you want to log changes of case temperature too?
yes it make sense.
>
>> + (verbose > 0 && level >= 0)) {
>> + print_temp("CPU-temp: ", temp );
>> + if (casetemp)
>> + print_temp(", Case: ", casetemp );
>> + if (level >= 0)
>> + printk(", Fan: %d (tuned %+d)\n", 11-level,
>> + x.fan_level-level );
>> + else
>> + printk(", Fan: %d (tuned +0)\n",x.fan_level);
>
> I think you can do without the "tuned +0" which doesn't add much value.
Me too. But the old driver does the same, so I preferred to
leave it as is.
>
>> + }
>> +
>> + x.temp = temp;
>> + x.casetemp = casetemp;
>> +
>> if( level >= 0 )
>> tune_fan( level );
>> }
>
>
--
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2014-08-03 15:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 14:00 [PATCH][v2] therm_windtunnel doesn't work properly on PowerMac G4 Goffredo Baroncelli
2014-08-01 14:00 ` [PATCH 1/4] Update drivers names to the ones invoked by i2c-powermac Goffredo Baroncelli
2014-08-01 14:00 ` [PATCH 2/4] Remove attach_method because un-used Goffredo Baroncelli
2014-08-01 14:00 ` [PATCH 3/4] Add the "verbose" module option Goffredo Baroncelli
2014-08-03 14:12 ` Jean Delvare
2014-08-03 15:12 ` Goffredo Baroncelli [this message]
2014-08-03 15:52 ` Jean Delvare
2014-08-03 16:36 ` Goffredo Baroncelli
2014-08-04 8:46 ` Jean Delvare
2014-08-04 17:10 ` Goffredo Baroncelli
2014-08-05 8:59 ` Jean Delvare
2014-08-01 14:00 ` [PATCH 4/4] Return the fan speed via sysfs Goffredo Baroncelli
2014-08-03 14:17 ` Jean Delvare
2014-08-03 15:27 ` Goffredo Baroncelli
2014-08-03 15:59 ` Jean Delvare
2014-08-03 16:42 ` Goffredo Baroncelli
2014-08-04 8:44 ` 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=53DE5179.3080402@gmail.com \
--to=kreijack@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=bryan@whatroute.net \
--cc=jdelvare@suse.de \
--cc=kreijack@inwind.it \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).