From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, alsa-devel@alsa-project.org,
tiwai@suse.de, Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] ASoC: SOF: ipc4-topology: Use correct queue_id for requesting input pin format
Date: Mon, 24 Jun 2024 17:26:32 +0200 [thread overview]
Message-ID: <7372501f-0393-4ba5-9e05-71d59dc1449b@linux.intel.com> (raw)
In-Reply-To: <ec992bf9-667c-48a4-81ed-3a1232123987@sirena.org.uk>
On 6/24/24 14:36, Mark Brown wrote:
> On Mon, Jun 24, 2024 at 02:15:18PM +0200, Pierre-Louis Bossart wrote:
>> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
>> Reviewed-by: Bard Liao <yung-chuan.liao@linux.intel.com>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
>> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> Cc: <stable@vger.kernel.org> # v6.8+
>> ---
>
> Please put fixes at the start of serieses, or send them separately -
> it makes things much easier to handle if they're separate. This ensures
> that the fixes don't end up with spurious dependencies on non-fix
> changes.
Agree, I wasn't sure if this was really linux-stable material, this
patch fixes problems on to-be-released topologies but it doesn't have
any effect on existing user setups. At the same time, it certainly fixes
a conceptual bug. Not sure if the tag is needed for those cases?
next prev parent reply other threads:[~2024-06-24 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 12:15 [PATCH 0/3] ASoC: SOF: topology/intel improvements Pierre-Louis Bossart
2024-06-24 12:15 ` [PATCH 1/3] ASoC: SOF: ipc4-topology: Use single token list for the copiers Pierre-Louis Bossart
2024-06-24 12:15 ` [PATCH 2/3] ASoC: SOF: ipc4-topology: Use correct queue_id for requesting input pin format Pierre-Louis Bossart
2024-06-24 12:36 ` Mark Brown
2024-06-24 15:26 ` Pierre-Louis Bossart [this message]
2024-06-24 18:11 ` Mark Brown
2024-06-24 12:15 ` [PATCH 3/3] ASoC: SOF: Intel: hda-pcm: Limit the maximum number of periods by MAX_BDL_ENTRIES Pierre-Louis Bossart
2024-06-25 11:33 ` (subset) [PATCH 0/3] ASoC: SOF: topology/intel improvements 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=7372501f-0393-4ba5-9e05-71d59dc1449b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
--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