From: Mark Brown <broonie@kernel.org>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, yung-chuan.liao@linux.intel.com,
lgirdwood@gmail.com, pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com, daniel.baluta@nxp.com
Subject: Re: [PATCH v2 2/3] ASoC: SOF: topology: don't use list_for_each_entry_reverse()
Date: Tue, 23 Nov 2021 18:08:23 +0000 [thread overview]
Message-ID: <YZ0uF3t9GJXIEO4L@sirena.org.uk> (raw)
In-Reply-To: <20211123171606.129350-2-kai.vehmanen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
On Tue, Nov 23, 2021 at 07:16:05PM +0200, Kai Vehmanen wrote:
> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> It's not clear why we would walk the list backwards. That makes no
> difference.
Cleanup patches like this should come after fixes rather than in the
middle of them to ensure that the fixes can be applied as such.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-23 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 17:16 [PATCH v2 1/3] ASoC: SOF: sof-audio: setup sched widgets during pipeline complete step Kai Vehmanen
2021-11-23 17:16 ` [PATCH v2 2/3] ASoC: SOF: topology: don't use list_for_each_entry_reverse() Kai Vehmanen
2021-11-23 18:08 ` Mark Brown [this message]
2021-11-23 17:16 ` [PATCH v2 3/3] ASoC: SOF: handle paused streams during system suspend Kai Vehmanen
2021-11-24 12:57 ` [PATCH v2 1/3] ASoC: SOF: sof-audio: setup sched widgets during pipeline complete step Mark Brown
2021-11-24 13:49 ` Kai Vehmanen
2021-11-24 17:36 ` Mark Brown
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=YZ0uF3t9GJXIEO4L@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.com \
/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.