lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <202209262009.D1377D0C3@keescook> Date: Mon, 26 Sep 2022 20:16:16 -0700 From: Kees Cook <keescook@...omium.org> To: Mark Brown <broonie@...nel.org> Cc: "Gustavo A. R. Silva" <gustavo@...eddedor.com>, "Gustavo A. R. Silva" <gustavoars@...nel.org>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH][next] ASoC: SOF: control.h: Replace zero-length array with DECLARE_FLEX_ARRAY() helper On Mon, Sep 26, 2022 at 11:39:50PM +0100, Mark Brown wrote: > On Mon, Sep 26, 2022 at 05:27:41PM -0500, Gustavo A. R. Silva wrote: > > On 9/26/22 17:12, Mark Brown wrote: > > > On Mon, Sep 26, 2022 at 04:40:55PM -0500, Gustavo A. R. Silva wrote: > > > > As documented in submitting-patches.rst please send patches to the > > > maintainers for the code you would like to change. The normal kernel > > > workflow is that people apply patches from their inboxes, if they aren't > > > copied they are likely to not see the patch at all and it is much more > > > difficult to apply patches. > > > That's exactly what I intended to do: > > > > $ scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback include/sound/sof/control.h > > Jaroslav Kysela <perex@...ex.cz> (maintainer:SOUND) > > Takashi Iwai <tiwai@...e.com> (maintainer:SOUND) > > alsa-devel@...a-project.org (moderated list:SOUND) > > linux-kernel@...r.kernel.org (open list) > > > > Did you see anything wrong with this or something...? > > Yes, you should've also included me and the SOF maintainers. It looks > like the MAINTAINERS patterns aren't entirely up to date there > unfortunately. Though that said given that you'd picked up on the > subject line I'd have expected the signoffs on the commits to also be > pointing at the right tree as well. Subject line heuristics look at X-many commits, but it looks like get_maintainers stops looking at git history by default after 1 year, which seems kind of odd. I had to work at it to get it to emit your name. :) scripts/get_maintainer.pl --git --git-since=3-years-ago Seems like it's worth getting the MAINTAINERS regex updated? Is this right? diff --git a/MAINTAINERS b/MAINTAINERS index a34ec41fbf7a..2560dded0e3e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -19261,6 +19261,7 @@ F: Documentation/devicetree/bindings/sound/ F: Documentation/sound/soc/ F: include/dt-bindings/sound/ F: include/sound/soc* +F: include/sound/sof/ F: sound/soc/ SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS @@ -19275,6 +19276,7 @@ L: sound-open-firmware@...a-project.org (moderated for non-subscribers) S: Supported W: https://github.com/thesofproject/linux/ F: sound/soc/sof/ +F: include/sound/sof/ SOUNDWIRE SUBSYSTEM M: Vinod Koul <vkoul@...nel.org> -- Kees Cook
Powered by blists - more mailing lists