From: Daniel Baluta <daniel.baluta@gmail.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG)
Date: Tue, 14 Dec 2021 19:40:12 +0200 [thread overview]
Message-ID: <CAEnQRZBQdP53aHSCS35-SO6t_5fn3vX5OBqGtkwj9zP=sbwDMw@mail.gmail.com> (raw)
In-Reply-To: <11ed7f0f-ad5a-cae1-035c-23e5d3736818@linux.intel.com>
On Tue, Dec 14, 2021 at 7:26 PM Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
>
>
>
> On 12/14/21 11:21 AM, Daniel Baluta wrote:
> > Hi Randy,
> >
> > This should be fixed by https://github.com/thesofproject/linux/pull/3284
>
> no, this was precisely the change that exposed a new problem.
>
> https://github.com/thesofproject/linux/pull/3335 contains the suggested
> fix posted earlier. We should know tomorrow if the 0day bot finds any
> other issues.
>
> >
> > Let me quickly send this to alsa-devel.
Thanks Pierre. I have seen your PR now!
next prev parent reply other threads:[~2021-12-14 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 3:02 linux-next: Tree for Dec 13 broonie
2021-12-14 6:20 ` linux-next: Tree for Dec 13 (SND_AMD_ACP_CONFIG) Randy Dunlap
2021-12-14 13:51 ` Pierre-Louis Bossart
2021-12-14 16:26 ` Randy Dunlap
2021-12-14 17:21 ` Daniel Baluta
2021-12-14 17:25 ` Pierre-Louis Bossart
2021-12-14 17:40 ` Daniel Baluta [this message]
2021-12-14 11:44 ` linux-next: Tree for Dec 13 Andy Shevchenko
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='CAEnQRZBQdP53aHSCS35-SO6t_5fn3vX5OBqGtkwj9zP=sbwDMw@mail.gmail.com' \
--to=daniel.baluta@gmail.com \
--cc=AjitKumar.Pandey@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rdunlap@infradead.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).