Re: [PATCH 00/20] ASoC: Intel: Use guard() for mutex & spin locks

[Bui Duc Phuc]

Hi Cezary,

Thank you for the guidance.

>
> Assuming someone is new to a subsystem (here, ASoC), it is advised to
> check the MAINTAINERS file and the kernel.org git repository list [1].
> In our case we're looking for sound/soc subsystem maintainer.  Both the
> file and the repository list will point out: Mark.  From there, fetch
> their "-next" branch, typically "for-next".  Checking out a for-next
> branch and applying proposed changed on top of it, recompiling and
> retesting solves majority of problems.
>

For future ASoC patches, I'll work on top of Mark's for-next branch.

>
> One could treat the conversion of open locking into guard() as
> "feature".  If a portion of such feature causes problems, it is usually
> better to revert the feature, fix the problems and apply it again.  When
> reverting, it's good to do so for the entire entity e.g.: the avs-driver.
>
> At the same time there may be no need to revert for everyone e.g.: the
> second driver, the atom-driver, if only the avs-driver presented
> problems.  Per-file would translate to quite a few reverts, again,
> unnecessary traffic.
>

Understood. I have a better understanding of how to handle Intel ASoC
patches now.

Best regards,
Phuc