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
| ||
|
Date: Fri, 05 Feb 2016 13:43:22 +0000 From: Måns Rullgård <mans@...sr.com> To: Mark Brown <broonie@...nel.org> Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] ASoC: mxs-saif: check BUSY bit in hw_params() only if not mclk_in_use Mark Brown <broonie@...nel.org> writes: > On Fri, Feb 05, 2016 at 01:23:20PM +0000, Måns Rullgård wrote: >> Mark Brown <broonie@...nel.org> writes: > >> > Please remember to CC the maintainers for the driver when sending >> > patches. > >> I CCd everybody scripts/get_maintainers.pl suggested. How am I supposed >> to know who the maintainers are if they're not listed in MAINTAINERS? > > By looking at people working on the driver in git and the authors listed > in the driver (get_maintainer --git will do most of this for you, though > you do have to think about false positives). As previously advised this > is not something that can be fully automated, you need to think about > who you are sending things to and why. Most files have been touched by many people. I thought the entire point of the MAINTAINERS file was to remove the guesswork from choosing where to send patches. Apparently sound/ has rules of its own. -- Måns Rullgård
Powered by blists - more mailing lists