On 12/10/23 16:01, Mark Brown wrote:
On Sun, Dec 10, 2023 at 12:12:53PM +0200, Cristian Ciocaltea wrote:Thanks for clarifying, Mark! That would greatly simplify and speedup
On 12/10/23 11:51, Venkata Prasad Potturu wrote:The SOF people basically do their own thing in github at
This should send to SOF git repo for rewiew, once SOF reviewers approvedUnfortunately I'm not familiar with the SOF dev workflow. So it's not
this, again need to send to broonie git.
All the changes in sound/soc/sof/ path should go to SOF git.
enough to have this patch cc-ed to sound-open-firmware@xxxxxxxxxxxxxxxx?
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.
the whole process, at least for trivial patches like this one.