From: Hanjun Guo <guohanjun@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: <linux-acpi@vger.kernel.org>, Ken Xue <Ken.Xue@amd.com>,
Hanjun Guo <guohanjun@huawei.com>
Subject: [PATCH 1/5] ACPI / APD: Add kernel doc for the properties in struct apd_device_desc
Date: Mon, 7 Sep 2020 16:56:17 +0800 [thread overview]
Message-ID: <1599468981-17301-2-git-send-email-guohanjun@huawei.com> (raw)
In-Reply-To: <1599468981-17301-1-git-send-email-guohanjun@huawei.com>
commit 7ff55d174cbf ("ACPI / APD: Provide build-in properties of the
UART") add the 'struct property_entry *properties' in struct
apd_device_desc but didn't add the kernel doc, add it now.
Signed-off-by: Hanjun Guo <guohanjun@huawei.com>
---
drivers/acpi/acpi_apd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/acpi/acpi_apd.c b/drivers/acpi/acpi_apd.c
index 4c34837..6f39289 100644
--- a/drivers/acpi/acpi_apd.c
+++ b/drivers/acpi/acpi_apd.c
@@ -34,6 +34,7 @@
* @flags: device flags like %ACPI_APD_SYSFS, %ACPI_APD_PM
* @fixed_clk_rate: fixed rate input clock source for acpi device;
* 0 means no fixed rate input clock source
+ * @properties: build-in properties of the device such as UART
* @setup: a hook routine to set device resource during create platform device
*
* Device description defined as acpi_device_id.driver_data
--
1.7.12.4
next prev parent reply other threads:[~2020-09-07 9:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 8:56 [PATCH 0/5] Cleanups for ACPI APD driver Hanjun Guo
2020-09-07 8:56 ` Hanjun Guo [this message]
2020-09-07 8:56 ` [PATCH 2/5] ACPI / APD: Remove the flags in struct apd_device_desc Hanjun Guo
2020-09-07 8:56 ` [PATCH 3/5] ACPI / APD: Remove ACPI_MODULE_NAME() Hanjun Guo
2020-09-07 8:56 ` [PATCH 4/5] ACPI / APD: Remove the unneeded APD_ADDR(desc) macro define Hanjun Guo
2020-09-07 8:56 ` [PATCH 5/5] ACPI / APD: Head file including cleanups Hanjun Guo
2020-09-07 11:19 ` kernel test robot
2020-09-07 12:29 ` Hanjun Guo
2020-09-07 13:07 ` kernel test robot
2020-09-09 0:54 ` Hanjun Guo
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=1599468981-17301-2-git-send-email-guohanjun@huawei.com \
--to=guohanjun@huawei.com \
--cc=Ken.Xue@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.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).