From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: unlisted-recipients:; (no To-header on input)
Cc: Jack Lo <jack.lo@gtsys.com.hk>,
devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] shtc1: add support for device tree bindings
Date: Tue, 7 Jul 2020 16:03:47 +0800 [thread overview]
Message-ID: <c7f4805a-0cdf-ea5b-7557-c4f00fec6ee8@gtsys.com.hk> (raw)
In-Reply-To: <20200707080104.23711-1-chris.ruehl@gtsys.com.hk>
On 7/7/2020 4:01 pm, Chris Ruehl wrote:
> Add support for DTS bindings to the shtc driver
> The patches add the compatible table and of_property_read_bool to the
> shtc1.c. Newly created Yaml document has been released to the
> Documentation/devicetree/hwmon/sensirion,shtc1.yaml
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
> Version 3
> Fix errors report with checkpatch.pl
> Correct logic, add (!) when check for sensirion,low_precision
> Version 2
> remove the #ifdef CONFIG_OF
> ignore platform data if dev->of_node is valid
> use boolean only therefor use sensirion,low_precise to fit the logic
> add missing driver.of_match_table entry
> Version 1
> initial version
>
I didn't fix the WARNINGS coming up with checkpatch, they are initial commit
errors when added to the kernel.
But I have a patch pending to fix the format issue , once this is accepted.
prev parent reply other threads:[~2020-07-07 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 8:01 [PATCH v3 0/2] shtc1: add support for device tree bindings Chris Ruehl
2020-07-07 8:01 ` [PATCH v3 1/2] hwmon: " Chris Ruehl
2020-07-07 8:01 ` [PATCH v3 2/2] devicetree: hwmon: shtc1: Add sensirion,shtc1.yaml Chris Ruehl
2020-07-07 8:03 ` Chris Ruehl [this message]
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=c7f4805a-0cdf-ea5b-7557-c4f00fec6ee8@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=jack.lo@gtsys.com.hk \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).