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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 23 May 2016 09:07:14 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	Lee Jones <lee@...nel.org>, Eric Anholt <eric@...olt.net>,
	linux-rpi-kernel@...ts.infradead.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 07/54] MAINTAINERS: Add file patterns for bcm2835 device
 tree bindings

On 05/22/2016 03:05 AM, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.


> @@ -2505,6 +2505,7 @@ L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git
>  S:	Maintained
>  N:	bcm2835
> +F:	Documentation/devicetree/bindings/soc/bcm/

This looks wrong; the kernel supports more Broadcom chips than just the 
bcm283[567]. I'd suggest using a regex to make sure it only matches the 
appropriate chips. Perhaps:

N: bcm283[567]

? That also has the advantage of matching all the bindings in other 
directories in Documentation/devicetree/bindings, and indeed all the 
drivers and DT files too.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ