From: Hugh Dickins <hughd@google.com>
To: Wolfram Sang <wsa@kernel.org>, Hugh Dickins <hughd@google.com>,
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 12:41:55 -0800 (PST) [thread overview]
Message-ID: <62e369a0-831e-1346-3d8-c394fc49ddf6@google.com> (raw)
In-Reply-To: <YgF/0QGFN4SppLKg@shikoro>
On Mon, 7 Feb 2022, Wolfram Sang wrote:
> 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?
Many thanks for such quick response (I found it at rc1, but couldn't
spend time to bisect until yesterday). Willing to test? Absolutely.
Hugh
next prev parent reply other threads:[~2022-02-07 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 19:45 Hugh Dickins
2022-02-07 20:23 ` Wolfram Sang
2022-02-07 20:41 ` Hugh Dickins [this message]
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=62e369a0-831e-1346-3d8-c394fc49ddf6@google.com \
--to=hughd@google.com \
--cc=dbasehore@chromium.org \
--cc=dmitry.torokhov@gmail.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 \
--cc=wsa@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
all inboxes | Powered by JetHome®