All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasa Ostrouska <casaxa@gmail.com>
To: Lukasz Majczak <lma@semihalf.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org,  regressions@lists.linux.dev,
	 Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	 Cezary Rojewski <cezary.rojewski@intel.com>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Tue, 24 Jan 2023 22:38:01 +0100	[thread overview]
Message-ID: <CALFERdwXwJxZ=jG=p6J1LUERzL9=xaiixN1t4Ux11axMW3CJuw@mail.gmail.com> (raw)
In-Reply-To: <CALFERdwpbQdpnyLuHxo67S4KC=if97AzLGDRVEo+u-HN2Tu0fg@mail.gmail.com>

On Tue, Jan 24, 2023 at 3:31 PM Sasa Ostrouska <casaxa@gmail.com> wrote:
>
> On Tue, Jan 24, 2023 at 1:11 PM Lukasz Majczak <lma@semihalf.com> wrote:
> >
> > > If you need anything else just let me know.
> > >
> > > Thanks
> > > Sasa
> >
> > Sasa,
> >
> > Thank you for sharing logs from the working version - could you also
> > provide dmesg for the no sound scenario? You can also share them using
> > e.g. https://gist.github.com/ .
>
> Lukasz thanks, sure, will provide that too but let me reboot into the
> non working kernel.
> Will post it on gist.github.com and post the link here.
>
Hi Lukasz, please see the dmesg with the non working sound kernel:
https://gist.github.com/saxa/08b233a95d5e52046354b07d2e9ca13d

> Rgds
> Sasa
> >
> > Best regards,
> > Lukasz

  reply	other threads:[~2023-01-24 21:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 20:44 Google Pixelbook EVE, no sound in kernel 6.1.x 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 [this message]
2023-01-25 15:48             ` Lukasz Majczak
2023-01-25 20:48               ` Sasa Ostrouska
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
2023-01-28 17:09 Jason Montleon
2023-01-28 17:52 ` 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)

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='CALFERdwXwJxZ=jG=p6J1LUERzL9=xaiixN1t4Ux11axMW3CJuw@mail.gmail.com' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.