From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
lgirdwood@gmail.com,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: alsa-devel@alsa-project.org, ranjani.sridharan@linux.intel.com,
kai.vehmanen@linux.intel.com, rander.wang@intel.com
Subject: Re: [PATCH 0/3] ASoC: SOF: Intel: mtl: Enable multicore support
Date: Fri, 26 May 2023 15:50:49 -0500 [thread overview]
Message-ID: <145987ea-0706-9bca-dc75-803a0625a8a2@linux.intel.com> (raw)
In-Reply-To: <168487142215.278276.6191766858062306959.b4-ty@kernel.org>
Hi Mark,
> On Tue, 23 May 2023 13:32:14 +0300, Peter Ujfalusi wrote:
>> The following series will enable multicore support on MTL platforms similarly
>> to other Intel platforms.
>>
>> The TGL patch is included to simplify the core_put implementation.
>>
>> Multicore support can be enabled by updated topologies, with current set of
>> tplg files this series is not introducing any runtime change.
>>
>> [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
>
> Thanks!
Looks like patch1 was not applied:
[PATCH 1/3] ASoC: SOF: Intel: mtl: setup primary core info on MeteorLake
platform
was there anything wrong with it or is this a b4/script issue?
Please let us know if we need to resend it or modify it.
Thanks,
-Pierre
> [2/3] ASoC: SOF: Intel: mtl: add core_get & put support on MeterLake platforms
> commit: c6d15567a4d5dd51ecccc332d514c6dc21bce652
> [3/3] ASoC: SOF: Intel: tgl: unify core_put on IPC3 & IPC4 path
> commit: 1b167ba8a20152041d3af0c0cbbfd710f1e93e4b
>
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
>
next prev parent reply other threads:[~2023-05-26 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 10:32 [PATCH 0/3] ASoC: SOF: Intel: mtl: Enable multicore support Peter Ujfalusi
2023-05-23 10:32 ` [PATCH 1/3] ASoC: SOF: Intel: mtl: setup primary core info on MeteorLake platform Peter Ujfalusi
2023-05-23 10:32 ` [PATCH 2/3] ASoC: SOF: Intel: mtl: add core_get & put support on MeterLake platforms Peter Ujfalusi
2023-05-23 10:32 ` [PATCH 3/3] ASoC: SOF: Intel: tgl: unify core_put on IPC3 & IPC4 path Peter Ujfalusi
2023-05-23 19:50 ` [PATCH 0/3] ASoC: SOF: Intel: mtl: Enable multicore support Mark Brown
2023-05-26 20:50 ` Pierre-Louis Bossart [this message]
2023-05-30 10: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=145987ea-0706-9bca-dc75-803a0625a8a2@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=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=ranjani.sridharan@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