From: Mark Brown <broonie@kernel.org>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC updates for v5.10
Date: Wed, 21 Oct 2020 13:22:09 +0100 [thread overview]
Message-ID: <20201021122209.GC4497@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2010211150040.864696@eliteleevi.tm.intel.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On Wed, Oct 21, 2020 at 12:26:22PM +0300, Kai Vehmanen wrote:
> maybe bundling the warning suppression to the same patchset was not the
> best of ideas. Jaroslav is correct the warnings can unfortunately create
> real confusion as this is on a code path we run on every rt-resume, and if
> you happen to have a system with FW that has some custom IPC types, you'll
> get this warning constantly in dmesg.
No, and especially putting it at the end of the series - presumably it
has dependencies on the rest of it? You should always put fixes first
in a series.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-21 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 13:08 [GIT PULL] ASoC updates for v5.10 Mark Brown
2020-10-12 13:16 ` Jaroslav Kysela
2020-10-12 13:28 ` Mark Brown
2020-10-21 8:23 ` Jaroslav Kysela
2020-10-21 9:26 ` Kai Vehmanen
2020-10-21 12:22 ` Mark Brown [this message]
2020-10-21 15:11 ` Kai Vehmanen
2020-10-21 16:48 ` Mark Brown
2020-10-21 11:59 ` Mark Brown
2020-10-12 15:04 ` Takashi Iwai
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=20201021122209.GC4497@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
/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.