From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, opendmb@gmail.com,
bcm-kernel-feedback-list@broadcom.com,
"Jiri Slaby" <jirislaby@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Eric Tremblay" <etremblay@distech-controls.com>,
"Wander Lairson Costa" <wander@redhat.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH] serial: 8250: Add missing wakeup event reporting
Date: Fri, 14 Apr 2023 05:54:06 -0700 [thread overview]
Message-ID: <fd092a59-dc44-2c26-5c72-c9b442cf2bc8@gmail.com> (raw)
In-Reply-To: <ZDj-htAWWxJ5gqPr@kroah.com>
On 4/14/2023 12:19 AM, Greg Kroah-Hartman wrote:
> On Thu, Apr 13, 2023 at 02:39:54PM -0700, Florian Fainelli wrote:
>> An 8250 UART configured as a wake-up source would not have reported
>> itself through sysfs as being the source of wake-up, correct that.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> drivers/tty/serial/8250/8250_port.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>
> What commit does this fix? Is it needed to go to stable kernel(s)?
That would be b3b708fa2780cd2b5d8266a8f0c3a1cab364d4d2 ("wake up from a
serial port").
I do not know of standard Linux distribution user-space relying on the
wake-up counts from sysfs, though I certainly do care.
The patch I submitted should backport fine all the way down to 4.14
where irqd_is_wakeup_set is available. Do you want me to submit a v2
with that Fixes tag?
--
Florian
prev parent reply other threads:[~2023-04-14 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 21:39 Florian Fainelli
2023-04-14 7:19 ` Greg Kroah-Hartman
2023-04-14 12:54 ` Florian Fainelli [this message]
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=fd092a59-dc44-2c26-5c72-c9b442cf2bc8@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=etremblay@distech-controls.com \
--cc=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=opendmb@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wander@redhat.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
all inboxes | Powered by JetHome®