From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bastian Rieck <bastian@rieck.me>,
grzegorz.alibozek@gmail.com, andrew.co@free.fr,
meven29@gmail.com, pchernik@gmail.com, jorge.cep.mart@gmail.com,
danielmorgan@disroot.org, bernie@codewiz.org,
saipavanchitta1998@gmail.com, rubin@starset.net,
maniette@gmail.com, nate@kde.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v1 0/2] usb: typec: UCSI resume fix
Date: Mon, 10 Oct 2022 10:52:24 +0300 [thread overview]
Message-ID: <Y0PPOBFFuWzFj0Oy@kuha.fi.intel.com> (raw)
In-Reply-To: <Y0A6Pb5owOWVVQET@kroah.com>
On Fri, Oct 07, 2022 at 04:39:57PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Oct 07, 2022 at 01:09:49PM +0300, Heikki Krogerus wrote:
> > Hi Greg,
> >
> > These two patches fix an issue where the ucsi drivers fail to detect
> > changes on the connection status (connections/disconnections) that
> > happen while the system is suspended.
> >
> >
> > Heikki Krogerus (2):
> > usb: typec: ucsi: Check the connection on resume
> > usb: typec: ucsi: acpi: Implement resume callback
> >
> > drivers/usb/typec/ucsi/ucsi.c | 42 +++++++++++++++++++++---------
> > drivers/usb/typec/ucsi/ucsi_acpi.c | 10 +++++++
> > 2 files changed, 39 insertions(+), 13 deletions(-)
>
> These are ok to go in after -rc1, right?
Yes, I think so.
thanks,
--
heikki
prev parent reply other threads:[~2022-10-10 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 10:09 [PATCH v1 0/2] usb: typec: UCSI resume fix Heikki Krogerus
2022-10-07 10:09 ` [PATCH v1 1/2] usb: typec: ucsi: Check the connection on resume Heikki Krogerus
2022-10-07 10:09 ` [PATCH v1 2/2] usb: typec: ucsi: acpi: Implement resume callback Heikki Krogerus
2022-10-07 14:39 ` [PATCH v1 0/2] usb: typec: UCSI resume fix Greg Kroah-Hartman
2022-10-10 7:52 ` Heikki Krogerus [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=Y0PPOBFFuWzFj0Oy@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andrew.co@free.fr \
--cc=bastian@rieck.me \
--cc=bernie@codewiz.org \
--cc=danielmorgan@disroot.org \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.alibozek@gmail.com \
--cc=jorge.cep.mart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maniette@gmail.com \
--cc=meven29@gmail.com \
--cc=nate@kde.org \
--cc=pchernik@gmail.com \
--cc=rubin@starset.net \
--cc=saipavanchitta1998@gmail.com \
--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