2023-10-04 19:34:56

by Kees Cook

[permalink] [raw]
Subject: [PATCH] MAINTAINERS: Include additional ASoC paths

Make sure a few other paths are correctly sent to the ASoC maintainers.

Link: https://lore.kernel.org/lkml/[email protected]/
Cc: Mark Brown <[email protected]>
Signed-off-by: Kees Cook <[email protected]>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 5f18ed0fbd42..585a13b9b52a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20116,6 +20116,8 @@ F: Documentation/devicetree/bindings/sound/
F: Documentation/sound/soc/
F: include/dt-bindings/sound/
F: include/sound/soc*
+F: include/sound/sof/
+F: include/uapi/sound/asoc.h
F: sound/soc/

SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS
--
2.34.1


2023-10-04 19:40:09

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: Include additional ASoC paths

On Wed, Oct 04, 2023 at 12:34:45PM -0700, Kees Cook wrote:

> +++ b/MAINTAINERS
> @@ -20116,6 +20116,8 @@ F: Documentation/devicetree/bindings/sound/
> F: Documentation/sound/soc/
> F: include/dt-bindings/sound/
> F: include/sound/soc*
> +F: include/sound/sof/
> +F: include/uapi/sound/asoc.h
> F: sound/soc/

The SOF header is also missing from the entry for SOF.


Attachments:
(No filename) (381.00 B)
signature.asc (499.00 B)
Download all attachments

2023-10-04 19:41:38

by Kees Cook

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: Include additional ASoC paths

On October 4, 2023 12:40:00 PM PDT, Mark Brown <[email protected]> wrote:
>On Wed, Oct 04, 2023 at 12:34:45PM -0700, Kees Cook wrote:
>
>> +++ b/MAINTAINERS
>> @@ -20116,6 +20116,8 @@ F: Documentation/devicetree/bindings/sound/
>> F: Documentation/sound/soc/
>> F: include/dt-bindings/sound/
>> F: include/sound/soc*
>> +F: include/sound/sof/
>> +F: include/uapi/sound/asoc.h
>> F: sound/soc/
>
>The SOF header is also missing from the entry for SOF.

Ah, right! Can you take this and tweak it with the missing entries, or should I send a v2?

-Kees


--
Kees Cook

2023-10-04 19:46:38

by Gustavo A. R. Silva

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: Include additional ASoC paths



On 10/4/23 21:34, Kees Cook wrote:
> Make sure a few other paths are correctly sent to the ASoC maintainers.
>
> Link: https://lore.kernel.org/lkml/[email protected]/
> Cc: Mark Brown <[email protected]>
> Signed-off-by: Kees Cook <[email protected]>

Acked-by: Gustavo A. R. Silva <[email protected]>

Thanks!
--
Gustavo

> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5f18ed0fbd42..585a13b9b52a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -20116,6 +20116,8 @@ F: Documentation/devicetree/bindings/sound/
> F: Documentation/sound/soc/
> F: include/dt-bindings/sound/
> F: include/sound/soc*
> +F: include/sound/sof/
> +F: include/uapi/sound/asoc.h
> F: sound/soc/
>
> SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS

2023-10-04 20:01:53

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: Include additional ASoC paths

On Wed, Oct 04, 2023 at 12:41:14PM -0700, Kees Cook wrote:

> >The SOF header is also missing from the entry for SOF.

> Ah, right! Can you take this and tweak it with the missing entries, or should I send a v2?

Could you send an incremental patch please? It's already in my CI as
is.


Attachments:
(No filename) (295.00 B)
signature.asc (499.00 B)
Download all attachments

2023-10-06 14:25:59

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] MAINTAINERS: Include additional ASoC paths

On Wed, 04 Oct 2023 12:34:45 -0700, Kees Cook wrote:
> Make sure a few other paths are correctly sent to the ASoC maintainers.
>
>

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] MAINTAINERS: Include additional ASoC paths
commit: 2175362f594bc8d3764c8108b1a0b88d0a56610a

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