From: "Laurențiu Păncescu" <lpancescu@gmail.com>
To: Salvatore Bonaccorso <carnil@debian.org>, Greg KH <greg@kroah.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Backporting fix for #199981 to 4.19.y?
Date: Sun, 6 Jun 2021 18:04:37 +0200 [thread overview]
Message-ID: <3f78a7b2-1b5a-17d2-b862-09fbb53fa409@gmail.com> (raw)
In-Reply-To: <YLzAw27CQpdEshBl@eldamar.lan>
Hi Salvatore, Greg,
On 6/6/21 2:34 PM, Salvatore Bonaccorso wrote:
> Instead of doing a specific backport, maybe it is enough to pick
> a46393c02c76 ("ACPI: probe ECDT before loading AML tables regardless
> of module-level code flag") frst on 4.19.y and then the mentioned fix
> b1c0330823fe ("ACPI: EC: Look for ECDT EC after calling
> acpi_load_tables()").
Many thanks for looking into this. I cherry-picked
d737f333b211361b6e239fc753b84c3be2634aaa and
b1c0330823fe842dbb34641f1410f0afa51c29d3 on linux-4.19.y, they indeed
apply cleanly as Salvatore wrote. I also compiled and tested the kernel,
the battery is correctly displayed as discharging when unplugged, with a
7.5 hours remaining as expected.
Does it still make sense for me to resubmit my patch with the "commit
<full SHA1 hash> upstream." comment fixed? I would trust upstream more
than me making one commit look reasonable while missing the other commit
it was based on. Greg, what would you prefer?
Best regards,
Laurențiu
next prev parent reply other threads:[~2021-06-06 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 7:53 Backporting fix for #199981 to 4.19.y? Laurențiu Păncescu
2021-06-03 8:07 ` Greg KH
2021-06-03 8:24 ` Laurențiu Păncescu
2021-06-03 9:19 ` Greg KH
2021-06-04 14:50 ` Laurențiu Păncescu
2021-06-04 15:42 ` Greg KH
2021-06-06 12:34 ` Salvatore Bonaccorso
2021-06-06 16:04 ` Laurențiu Păncescu [this message]
2021-06-08 14:35 ` Greg KH
2021-06-08 15:45 ` Laurențiu Păncescu
2021-06-08 16:57 ` Greg KH
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=3f78a7b2-1b5a-17d2-b862-09fbb53fa409@gmail.com \
--to=lpancescu@gmail.com \
--cc=carnil@debian.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--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