From: Wolfram Sang <wsa@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: Derek Basehore <dbasehore@chromium.org>,
Rajat Jain <rajatja@google.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thorsten Leemhuis <regressions@leemhuis.info>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: 5.17-rc regression: X1 Carbon touchpad not resumed
Date: Mon, 7 Feb 2022 21:23:45 +0100 [thread overview]
Message-ID: <YgF/0QGFN4SppLKg@shikoro> (raw)
In-Reply-To: <89456fcd-a113-4c82-4b10-a9bcaefac68f@google.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
Hello Hugh,
> Bisection led to 172d931910e1db800f4e71e8ed92281b6f8c6ee2
> ("i2c: enable async suspend/resume on i2c client devices")
> and reverting that fixes it for me.
Thank you for the report plus bisection and sorry for the regression!
I will wait a few days if people come up with a fix. If not, I will
revert the offending commit. Are you willing to test patches in case
there will be some?
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-07 20:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 19:45 5.17-rc regression: X1 Carbon touchpad not resumed Hugh Dickins
2022-02-07 20:23 ` Wolfram Sang [this message]
2022-02-07 20:41 ` Hugh Dickins
2022-02-07 21:09 ` 5.17-rc regression: rmi4 clients cannot deal with asynchronous suspend? (was: X1 Carbon touchpad not resumed) Rajat Jain
2022-02-07 21:41 ` Rajat Jain
2022-02-08 2:20 ` Dmitry Torokhov
2022-02-08 2:50 ` Hugh Dickins
2022-02-08 10:02 ` Loic Poulain
2022-02-08 14:57 ` Jarkko Nikula
2022-02-14 2:31 ` Dmitry Torokhov
2022-02-14 7:36 ` Hugh Dickins
2022-02-14 12:11 ` Jarkko Nikula
2022-02-14 8:57 ` Hans de Goede
2022-02-08 6:37 ` 5.17-rc regression: X1 Carbon touchpad not resumed Thorsten Leemhuis
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=YgF/0QGFN4SppLKg@shikoro \
--to=wsa@kernel.org \
--cc=dbasehore@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hughd@google.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajatja@google.com \
--cc=regressions@leemhuis.info \
/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;
as well as URLs for NNTP newsgroup(s).