linux-kernel - Re: Status of Subsystems - MICROCHIP SAMA5D2-COMPATIBLE PIOBU GPIO

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] [day] [month] [year] [list]

Message-ID: <f73f5db7-edcd-f579-ec2a-e42bf92c044d@microchip.com>
Date:   Fri, 23 Aug 2019 09:13:57 +0000
From:   <Nicolas.Ferre@...rochip.com>
To:     <sebastian.duda@....de>
CC:     <linux-gpio@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <lukas.bulwahn@...il.com>,
        <Ludovic.Desroches@...rochip.com>, <alexandre.belloni@...tlin.com>
Subject: Re: Status of Subsystems - MICROCHIP SAMA5D2-COMPATIBLE PIOBU GPIO

Sebastian,

On 20/08/2019 at 15:27, Sebastian Duda wrote:
> Hello Andrei,
> 
> in my master thesis, I'm using the association of subsystems to
> maintainers/reviewers and its status given in the MAINTAINERS file.
> During the research I noticed that there are several subsystems without
> a status in the maintainers file. One of them is the subsystem
> `MICROCHIP SAMA5D2-COMPATIBLE PIOBU GPIO` where you're mentioned as
> maintainer.
> 
> Is it intended not to mention a status for your subsystems?
> What is the current status of your subsystem?

I've just removed this entry and merged it with other gpio/pinctrl 
driver's entry:
https://lore.kernel.org/linux-arm-kernel/20190823083158.2649-1-nicolas.ferre@microchip.com/

Best regards,
-- 
Nicolas Ferre