From: Mark Brown <broonie@kernel.org>
To: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, kai.vehmanen@linux.intel.com,
lgirdwood@gmail.com, rander.wang@intel.com,
ranjani.sridharan@linux.intel.com,
yung-chuan.liao@linux.intel.com,
angelogioacchino.delregno@collabora.com
Subject: Re: [PATCH v2 0/3] ASoC: SOF: sof-audio: Fixes for widget prepare and unprepare
Date: Tue, 17 Jan 2023 14:18:23 +0000 [thread overview]
Message-ID: <Y8auL5VNefcFZAB4@sirena.org.uk> (raw)
In-Reply-To: <597d5cee-f9fd-411f-c780-8413b6fd422d@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On Tue, Jan 17, 2023 at 04:05:18PM +0200, Péter Ujfalusi wrote:
> It is the topology ops optionality stuff. It is in itself a trivial (for
> my eyes) conflict, but it is a conflict never the less.
> This is not going to backport cleanly to stable either.
> What would be the preferred way to handle this (for next, for 6.2 and
> for 6.1.x)?
Can you send me a version that applies against for-6.2, if it
doesn't backport to stable you can send an explicit backport
patch once that becomes an issue. I'm much happier resolving a
merge between 6.2 and 6.3 than on initial application.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-17 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 12:55 [PATCH v2 0/3] ASoC: SOF: sof-audio: Fixes for widget prepare and unprepare Peter Ujfalusi
2023-01-16 12:55 ` [PATCH v2 1/3] ASoC: SOF: sof-audio: Unprepare when swidget->use_count > 0 Peter Ujfalusi
2023-01-16 12:55 ` [PATCH v2 2/3] ASoC: SOF: sof-audio: skip prepare/unprepare if swidget is NULL Peter Ujfalusi
2023-01-17 12:44 ` AngeloGioacchino Del Regno
2023-01-16 12:55 ` [PATCH v2 3/3] ASoC: SOF: sof-audio: keep prepare/unprepare widgets in sink path Peter Ujfalusi
2023-01-17 13:16 ` [PATCH v2 0/3] ASoC: SOF: sof-audio: Fixes for widget prepare and unprepare Mark Brown
2023-01-17 13:48 ` Péter Ujfalusi
2023-01-17 14:05 ` Péter Ujfalusi
2023-01-17 14:18 ` Mark Brown [this message]
2023-01-17 14:30 ` Péter Ujfalusi
2023-01-17 15:21 ` Mark Brown
2023-01-18 15:46 ` 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=Y8auL5VNefcFZAB4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox