From: Mario Limonciello <mario.limonciello@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>,
Iain Lane <iain@orangesquash.org.uk>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v8 1/2] ACPI: Add comments to clarify some #ifdef statements
Date: Wed, 2 Aug 2023 15:10:12 -0500 [thread overview]
Message-ID: <20230802201013.910-2-mario.limonciello@amd.com> (raw)
In-Reply-To: <20230802201013.910-1-mario.limonciello@amd.com>
With nested #ifdef statements it's sometimes difficult to tell
which code goes with which statement. One comment was wrong,
so fix it and add another comment to clarify another.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
include/linux/acpi.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 641dc48439873..0d5277b7c6323 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -1117,10 +1117,10 @@ static inline void arch_reserve_mem_area(acpi_physical_address addr,
size_t size)
{
}
-#endif /* CONFIG_X86 */
+#endif /* CONFIG_IA64 */
#else
#define acpi_os_set_prepare_sleep(func, pm1a_ctrl, pm1b_ctrl) do { } while (0)
-#endif
+#endif /* CONFIG_ACPI */
#if defined(CONFIG_ACPI) && defined(CONFIG_PM)
int acpi_dev_suspend(struct device *dev, bool wakeup);
--
2.34.1
next prev parent reply other threads:[~2023-08-02 20:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 20:10 [PATCH v8 0/2] Fix wakeup problems on some AMD platforms Mario Limonciello
2023-08-02 20:10 ` Mario Limonciello [this message]
2023-08-02 20:10 ` [PATCH v8 2/2] PCI/ACPI: Use device constraints instead of dates to opt devices into D3 Mario Limonciello
2023-08-03 5:01 ` Mika Westerberg
2023-08-03 11:38 ` Mario Limonciello
2023-08-03 15:14 ` Mika Westerberg
2023-08-03 15:18 ` Mario Limonciello
2023-08-04 6:07 ` Mika Westerberg
2023-08-04 6:12 ` Andy Shevchenko
2023-08-04 12:59 ` Mario Limonciello
2023-08-04 2:32 ` Mario Limonciello
2023-08-03 5:04 ` kernel test robot
2023-08-03 9:40 ` kernel test robot
2023-08-03 11:49 ` 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=20230802201013.910-2-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=iain@orangesquash.org.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox