From: Greg KH <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
"Owen T . Heisler" <writer@owenh.net>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
linux-acpi@vger.kernel.org, regressions@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ACPI: PM: Add acpi_device_fix_up_power_children() function
Date: Mon, 13 Nov 2023 09:32:57 -0500 [thread overview]
Message-ID: <2023111349-outward-rectify-cb4e@gregkh> (raw)
In-Reply-To: <20231112203627.34059-2-hdegoede@redhat.com>
On Sun, Nov 12, 2023 at 09:36:26PM +0100, Hans de Goede wrote:
> In some cases it is necessary to fix-up the power-state of an ACPI
> device's children without touching the ACPI device itself add
> a new acpi_device_fix_up_power_children() function for this.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> drivers/acpi/device_pm.c | 13 +++++++++++++
> include/acpi/acpi_bus.h | 1 +
> 2 files changed, 14 insertions(+)
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-11-13 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 20:36 [PATCH 0/2] ACPI: video: Use acpi_device_fix_up_power_children() Hans de Goede
2023-11-12 20:36 ` [PATCH 1/2] ACPI: PM: Add acpi_device_fix_up_power_children() function Hans de Goede
2023-11-13 14:32 ` Greg KH [this message]
2023-11-12 20:36 ` [PATCH 2/2] ACPI: video: Use acpi_device_fix_up_power_children() Hans de Goede
2023-11-12 22:35 ` kernel test robot
2023-11-20 16:32 ` [PATCH 0/2] " Rafael J. Wysocki
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=2023111349-outward-rectify-cb4e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=writer@owenh.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 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.