From: Greg KH <gregkh@linuxfoundation.org>
To: Joshua Freedman <freedman.joshua@gmail.com>
Cc: lis8215@gmail.com, paul@crapouillou.net, stable@vger.kernel.org,
sboyd@kernel.org
Subject: Re: kernel 5.16.12 and above broke yoga c930 sound and mic
Date: Fri, 1 Apr 2022 12:47:12 +0200 [thread overview]
Message-ID: <YkbYMBpNztYHUsD2@kroah.com> (raw)
In-Reply-To: <CAJQ3t4Rg2WhDoynG=NmHX5dgt3u5BB3gfpAbskb4gQ_R8qxmxA@mail.gmail.com>
On Wed, Mar 30, 2022 at 04:54:53PM -0400, Joshua Freedman wrote:
> This felt really anti-climactic haha, but hopefully it's useful?
> cat bisect.log
> Bisecting: 81 revisions left to test after this (roughly 6 steps)
> [770aac3c84e0c83a19985413fa9fbfc126cc0ff6] net: mdio-ipq4019: add delay
> after clock enable
Wait, you still have more steps to go here. Did you test this kernel?
If so, you need to continue using 'git bisect good' and 'git bisect bad'
to find the offending commit. This looks just like the first step?
thanks,
greg k-h
next prev parent reply other threads:[~2022-04-01 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJQ3t4RxYXkREhwBb_JgYj4=ty+VtnV9m65U79ZLbmmj4mN7WA@mail.gmail.com>
2022-03-30 8:26 ` kernel 5.16.12 and above broke yoga c930 sound and mic Greg KH
[not found] ` <CAJQ3t4TqK+q5zeHCQ2uxGvhT4q0Bpe6PBuDTm28HqyHwH5mzhQ@mail.gmail.com>
2022-03-30 9:47 ` Greg KH
[not found] ` <CAJQ3t4SnNyHEaWizzVDbaMSdHDRe9wHGx2RdgJJea=G4sFmdnw@mail.gmail.com>
2022-03-30 11:02 ` Greg KH
[not found] ` <CAJQ3t4Rg2WhDoynG=NmHX5dgt3u5BB3gfpAbskb4gQ_R8qxmxA@mail.gmail.com>
2022-04-01 10:46 ` Greg KH
2022-04-01 10:47 ` Greg KH [this message]
[not found] ` <CAJQ3t4Q3ToQ9_Y3qc2WTsgxD9D14F-x4X5gTDB-mEWXqbeCk=g@mail.gmail.com>
2022-04-11 9:37 ` Greg KH
[not found] ` <CAJQ3t4Sf3fLqxrpwvmZ9KCgfXVTdaxaUcG1U_gEK+xDo3+BHxQ@mail.gmail.com>
2022-04-22 12:09 ` Greg KH
2022-03-30 8:56 ` Paul Cercueil
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=YkbYMBpNztYHUsD2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=freedman.joshua@gmail.com \
--cc=lis8215@gmail.com \
--cc=paul@crapouillou.net \
--cc=sboyd@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