From: Jason Montleon <jmontleo@redhat.com>
To: gregkh@linuxfoundation.org
Cc: casaxa@gmail.com, cezary.rojewski@intel.com, lma@semihalf.com,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Sat, 28 Jan 2023 12:09:54 -0500 [thread overview]
Message-ID: <CAJD_bPJ1VYTSQvogui4S9xWn9jQzQq8JRXOzXmus+qoRyrybOA@mail.gmail.com> (raw)
I did a bisect which implicated
f2bd1c5ae2cb0cf9525c9bffc0038c12dd7e1338 as the first bad commit.
Reverting this commit on 6.1.8 gives me working sound again.
I'm not clear why this is breaking 6.1.x since it appears to be in
6.0.18 (7494e2e6c55e), which was the last working package in Fedora
for the 6.0 line. Maybe something else didn't make it into 6.1?
next reply other threads:[~2023-01-28 17:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 17:09 Jason Montleon [this message]
2023-01-28 17:52 ` Google Pixelbook EVE, no sound in kernel 6.1.x Greg KH
2023-01-29 0:23 ` Jason Montleon
2023-01-30 6:33 ` Jason Montleon
2023-01-30 11:27 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-30 12:15 ` Cezary Rojewski
2023-01-30 12:22 ` Sasa Ostrouska
2023-01-31 12:36 ` Cezary Rojewski
2023-01-31 14:58 ` Sasa Ostrouska
2023-01-31 15:48 ` Cezary Rojewski
2023-01-31 16:02 ` Sasa Ostrouska
2023-01-31 15:16 ` Jason Montleon
2023-01-31 15:46 ` Cezary Rojewski
2023-02-01 11:05 ` Amadeusz Sławiński
2023-02-01 14:33 ` Jason Montleon
2023-02-04 15:16 ` Jason Montleon
2023-02-06 9:03 ` Amadeusz Sławiński
2023-02-06 13:51 ` Jason Montleon
2023-02-06 19:57 ` Jason Montleon
2023-02-06 21:15 ` Sasa Ostrouska
2023-02-09 16:13 ` Jason Montleon
2023-02-09 19:22 ` Jason Montleon
2023-02-10 13:09 ` Cezary Rojewski
2023-02-10 14:56 ` Jason Montleon
2023-02-10 17:15 ` Sasa Ostrouska
2023-01-30 11:23 ` Linux kernel regression tracking (#update)
-- strict thread matches above, loose matches on Subject: below --
2023-01-23 20:44 Sasa Ostrouska
2023-01-24 5:09 ` Greg KH
2023-01-24 10:18 ` Lukasz Majczak
2023-01-24 11:34 ` Sasa Ostrouska
2023-01-24 12:11 ` Lukasz Majczak
2023-01-24 14:31 ` Sasa Ostrouska
2023-01-24 21:38 ` Sasa Ostrouska
2023-01-25 15:48 ` Lukasz Majczak
2023-01-24 11:30 ` Sasa Ostrouska
2023-01-26 12:59 ` Linux kernel regression tracking (#adding)
2023-01-27 10:06 ` Sasa Ostrouska
2023-02-09 14:11 ` Sasa Ostrouska
2023-02-24 1:10 ` Sasa Ostrouska
2023-02-24 20:43 ` Sasa Ostrouska
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=CAJD_bPJ1VYTSQvogui4S9xWn9jQzQq8JRXOzXmus+qoRyrybOA@mail.gmail.com \
--to=jmontleo@redhat.com \
--cc=casaxa@gmail.com \
--cc=cezary.rojewski@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lma@semihalf.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).