From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Chris Lesiak <chris.lesiak@licor.com>,
Matt Ranostay <matt.ranostay@konsulko.com>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: humidity: hdc100x: Add ACPI HID table
Date: Thu, 6 Jan 2022 16:32:42 +0200 [thread overview]
Message-ID: <CAHp75VdxV+4_yxJv1H1MZPpu02e2gHUkP55dduUqN7QJ2j6aGg@mail.gmail.com> (raw)
In-Reply-To: <20220106041257.927664-1-kai.heng.feng@canonical.com>
On Thu, Jan 6, 2022 at 6:13 AM Kai-Heng Feng
<kai.heng.feng@canonical.com> wrote:
>
> x86 boards may use ACPI HID "TXN1010" to for hdc100x device.
to for --> for the
> So add an ACPI match table for that accordingly.
...
> - Change the ID to follow ACPI Spec
Is there any evidence Texas Instrument allocated this ID, or you just
created it yourself?
Please, add an excerpt from email from them to confirm this.
...
> +static const struct acpi_device_id __maybe_unused hdc100x_acpi_match[] = {
> + { "TXN1010" },
> + { },
No comma is needed.
> +};
> +
No blank line is needed.
> +MODULE_DEVICE_TABLE(acpi, hdc100x_acpi_match);
...
> + .acpi_match_table = ACPI_PTR(hdc100x_acpi_match),
It's the wrong usage of ACPI_PTR().
> },
All the comments are applicable to all your patches. Some of them I
already commented on and even kbuild bot has sent you a complaint.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-01-06 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 4:12 [PATCH v2] iio: humidity: hdc100x: Add ACPI HID table Kai-Heng Feng
2022-01-06 14:32 ` Andy Shevchenko [this message]
2022-01-07 4:14 ` Kai-Heng Feng
2022-01-07 10:35 ` Andy Shevchenko
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=CAHp75VdxV+4_yxJv1H1MZPpu02e2gHUkP55dduUqN7QJ2j6aGg@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=chris.lesiak@licor.com \
--cc=jic23@kernel.org \
--cc=kai.heng.feng@canonical.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.ranostay@konsulko.com \
/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.