On 10/12/23 19:31, Mark Brown wrote:

On Sun, Dec 10, 2023 at 12:12:53PM +0200, Cristian Ciocaltea wrote:

...

On 12/10/23 11:51, Venkata Prasad Potturu wrote:

...

This should send to SOF git repo for rewiew, once SOF reviewers approved this, again need to send to broonie git. All the changes in sound/soc/sof/ path should go to SOF git.

Unfortunately I'm not familiar with the SOF dev workflow. So it's not enough to have this patch cc-ed to sound-open-firmware@alsa-project.org?

The SOF people basically do their own thing in github at

https://github.com/thesofproject/linux

with a github workflow and submit their patches upstream in batches a few times a release, however my understanding is that their workflow can cope with things going in directly upstream as well.

If patches are directly pushed to alsa devel list instead of creating pull request for SOF patches It will break SOF github work flow. Validation across all the platforms is a potential challenge, and it will also create an overhead to pull the patches which got merged in to for-next branch, before the all the patches pulled in to SOF GitHub.