From: caesar.upstream@gmail.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/5] thermal: rockchip: fix a trivial typo
Date: Mon, 30 Nov 2015 10:32:18 +0800 [thread overview]
Message-ID: <565BB532.4010804@gmail.com> (raw)
In-Reply-To: <5259912.5mmETGszQg@diego>
Hi Heiko,
Thanks to take your time to review that.
? 2015?11?27? 17:49, Heiko St?bner ??:
> Hi Caesar,
>
> Am Freitag, 27. November 2015, 10:52:22 schrieb Caesar Wang:
[...]
>
> /**
> -* The conversion table has the adc value and temperature.
> -* ADC_DECREMENT is the adc value decremnet.(e.g. v2_code_table)
> -* ADC_INCREMNET is the adc value incremnet.(e.g. v3_code_table)
> -*/
> + * The conversion table has the adc value and temperature.
> + * ADC_DECREMENT: the adc value is of diminishing.(e.g. v2_code_table)
> + * ADC_INCREMENT: the adc value is incremental.(e.g. v3_code_table)
> + */
> enum adc_sort_mode {
> ADC_DECREMENT = 0,
> ADC_INCREMENT,
> @@ -75,13 +75,13 @@ enum adc_sort_mode {
> You could simply move to documenting the fields in the header (like
> exynos_tmu.c for example) instead of inside the table. I think there are even
> tools that create documention from these comments, so I'd suggest:
>
> /*
> * struct chip_tsadc_table: hold information about chip-specific differences
> * @id: conversion table
> * @length: size of conversion table
> * @data_mask: mask to apply on data inputs
> * @mode: sort mode of this adc variant (incrementing or decrementing)
> */
That's a good idea for this.
Fixed in next patch v2.
>> struct chip_tsadc_table {
>> const struct tsadc_table *id;
>>
>> - /* the array table size*/
>> + /* The array table size */
>> unsigned int length;
>>
>> - /* that analogic mask data */
>> + /* That analogic mask data */
>> u32 data_mask;
>>
>> - /* the sort mode is adc value that increment or decrement in table */
>> + /* The sort mode is adc value that increment or decrement in table */
>> enum adc_sort_mode mode;
>> };
>>
>> @@ -617,7 +617,7 @@ rockchip_thermal_register_sensor(struct platform_device
>> *pdev, return 0;
>> }
>>
>> -/*
>> +/**
>> * Reset TSADC Controller, reset all tsadc registers.
>> */
>> static void rockchip_thermal_reset_controller(struct reset_control *reset)
>
>
>
>
> --
> Thanks,
> Caesar
next prev parent reply other threads:[~2015-11-30 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 2:52 [PATCH v1 0/5] Fix a trivial typo and support rk3228/rk3399 SoCs for thermal driver Caesar Wang
2015-11-27 2:52 ` [PATCH v1 1/5] thermal: rockchip: fix a trivial typo Caesar Wang
2015-11-27 9:49 ` Heiko Stübner
2015-11-30 2:32 ` Caesar Wang [this message]
2015-11-27 2:52 ` [PATCH v1 2/5] thermal: rockchip: fix a impossible condition caused by the warning Caesar Wang
2015-11-27 2:52 ` [PATCH v1 3/5] dt-bindings: rockchip-thermal: Support the RK3228/RK3399 SoCs compatible Caesar Wang
2015-11-27 2:52 ` [PATCH v1 4/5] thermal: rockchip: Support the RK3228 SoCs in thermal driver Caesar Wang
2015-11-27 2:52 ` [PATCH v1 5/5] thermal: rockchip: Support the RK3399 " Caesar Wang
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=565BB532.4010804@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).