From: Sebastian Duda <sebastian.duda@fau.de>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: linux-kernel@vger.kernel.org, lukas.bulwahn@gmail.com
Subject: Re: Status of Subsystems
Date: Tue, 20 Aug 2019 15:56:24 +0200 [thread overview]
Message-ID: <3cf18665-7669-a33c-a718-e0917fa6d1b9@fau.de> (raw)
In-Reply-To: <20190820131422.2navbg22etf7krxn@pali>
On 20.08.19 15:14, Pali Rohár wrote:
> On Tuesday 20 August 2019 15:05:51 Sebastian Duda wrote:
>> Hello Pali,
>>
>> 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 `ALPS PS/2
>> TOUCHPAD DRIVER` where you're mentioned as reviewer.
>>
>> Is it intended not to mention a status for your subsystems?
>> What is the current status of these systems?
>>
>> Kind regards
>> Sebastian Duda
>
> Hi Sebastian! ALPS PS/2 is a driver for ALPS touchpad. They can be
> found on more laptops. And ALPS PS/2 itself is not separate subsystem.
> It is just driver which is part of kernel input subsystem with mailing
> list linux-input@vger.kernel.org.
>
Hi Pali,
so the status of the files is inherited from the subsystem `INPUT
MULTITOUCH (MT) PROTOCOL`?
Is it the same with the subsystem `NOKIA N900 POWER SUPPLY DRIVERS`
(respectively `POWER SUPPLY CLASS/SUBSYSTEM and DRIVERS`)?
Kind regards
Sebastian Duda
next prev parent reply other threads:[~2019-08-20 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 13:05 Sebastian Duda
2019-08-20 13:14 ` Pali Rohár
2019-08-20 13:56 ` Sebastian Duda [this message]
2019-08-20 14:05 ` Pali Rohár
2019-08-20 14:09 ` Joe Perches
2019-08-20 17:15 ` Theodore Y. Ts'o
2019-08-21 12:10 ` Enrico Weigelt, metux IT consult
2019-08-22 10:54 ` Sebastian Duda
2019-08-22 14:08 ` Theodore Y. Ts'o
2019-08-22 9:28 ` Sebastian Duda
2019-08-22 12:49 ` Enrico Weigelt, metux IT consult
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cf18665-7669-a33c-a718-e0917fa6d1b9@fau.de \
--to=sebastian.duda@fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pali.rohar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome