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

Message-ID: <d2bdb45a-3571-5989-8278-6f5c7d9839f2@fau.de>
Date:   Tue, 20 Aug 2019 15:27:29 +0200
From:   Sebastian Duda <sebastian.duda@....de>
To:     Andrei Stefanescu <andrei.stefanescu@...rochip.com>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org, lukas.bulwahn@...il.com
Subject: Status of Subsystems - MICROCHIP SAMA5D2-COMPATIBLE PIOBU GPIO

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?

Kind regards
Sebastian Duda