From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Hung <alex.hung@canonical.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org,
All applicable <stable@vger.kernel.org>
Subject: Re: [PATCH] ACPI: video: use ACPI backlight for HP 635 Notebook
Date: Sat, 12 Sep 2020 08:49:00 +0200 [thread overview]
Message-ID: <20200912064900.GB558156@kroah.com> (raw)
In-Reply-To: <20200911221420.21692-1-alex.hung@canonical.com>
On Fri, Sep 11, 2020 at 04:14:20PM -0600, Alex Hung wrote:
> Default backlight interface is AMD's radeon_bl0 which does not work on
> this system. As a result, let's for ACPI backlight interface for this
> system.
>
> BugLink: https://bugs.launchpad.net/bugs/1894667
>
> Cc: All applicable <stable@vger.kernel.org>
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
> drivers/acpi/video_detect.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/acpi/video_detect.c b/drivers/acpi/video_detect.c
> index 2499d7e..05047a3 100644
> --- a/drivers/acpi/video_detect.c
> +++ b/drivers/acpi/video_detect.c
> @@ -282,6 +282,15 @@ static const struct dmi_system_id video_detect_dmi_table[] = {
> DMI_MATCH(DMI_PRODUCT_NAME, "530U4E/540U4E"),
> },
> },
> + /* https://bugs.launchpad.net/bugs/1894667 */
> + {
> + .callback = video_detect_force_video,
> + .ident = "HP 635 Notebook",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "HP 635 Notebook PC"),
> + },
> + },
>
> /* Non win8 machines which need native backlight nevertheless */
> {
> --
> 2.7.4
>
<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:[~2020-09-12 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 22:14 [PATCH] ACPI: video: use ACPI backlight for HP 635 Notebook Alex Hung
2020-09-12 6:49 ` Greg KH [this message]
2020-09-13 22:33 ` Alex Hung
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=20200912064900.GB558156@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alex.hung@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stable@vger.kernel.org \
/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