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]
Message-ID: <b997e8e6-63a9-cdd0-9ef5-d0961ff09090@puri.sm>
Date:   Mon, 13 Jul 2020 09:14:13 +0200
From:   Martin Kepplinger <martin.kepplinger@...i.sm>
To:     Shawn Guo <shawnguo@...nel.org>
Cc:     robh@...nel.org, kernel@...i.sm, s.hauer@...gutronix.de,
        kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
        mchehab@...nel.org, Anson.Huang@....com, agx@...xcpu.org,
        angus@...ea.ca, broonie@...nel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 2/2] MAINTAINERS: Add Purism Librem 5 section to the
 list

On 11.07.20 15:40, Shawn Guo wrote:
> On Wed, Jun 17, 2020 at 09:38:21AM +0200, Martin Kepplinger wrote:
>> Add development information for the devicetree files for hardware
>> by Purism SPC.
>>
>> Signed-off-by: Martin Kepplinger <martin.kepplinger@...i.sm>
>> ---
>>  MAINTAINERS | 7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index b045b70e54df..0f6f18c477db 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -13881,6 +13881,13 @@ T:	git git://linuxtv.org/media_tree.git
>>  F:	Documentation/admin-guide/media/pulse8-cec.rst
>>  F:	drivers/media/cec/usb/pulse8/
>>  
>> +PURISM LIBREM 5
>> +M:	Purism Kernel Team <kernel@...i.sm>
>> +S:	Supported
>> +B:	https://source.puri.sm/Librem5/linux-next/issues
>> +T:	https://source.puri.sm/Librem5/linux-next
>> +F:	arch/arm64/boot/dts/freescale/imx8mq-librem5*
>> +
> 
> We do not generally patch MAINTAINERS for every single board.  Do you
> really want it?
> 

my aim was to point people to the kernel@...i.sm company email address
that is not used to send changes upstream (so not automatically picked
up by get_maintainer.py but will always deliver emails to the current
kernel team.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ