From: Jiri Slaby <jirislaby@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] MAINTAINERS: TTY LAYER: add some ./include/linux/ header files
Date: Tue, 18 May 2021 07:37:41 +0200 [thread overview]
Message-ID: <69da627e-91c5-66f0-c0c9-75fbaaba6782@kernel.org> (raw)
In-Reply-To: <20210518052117.14819-2-lukas.bulwahn@gmail.com>
On 18. 05. 21, 7:21, Lukas Bulwahn wrote:
> An early prototypical automated code analysis of headers and the
> existing MAINTAINERS sections identified some header files in
> ./include/linux/ to be probably included into the TTY LAYER section.
>
> I further checked those suggestions by this analysis and identified a
> subset of files that I am rather certain to belong to the TTY LAYER.
>
> Add these ./include/linux/ header files to TTY LAYER in MAINTAINERS.
>
> The patterns include/linux/tty*.h and include/linux/vt_*.h currently cover:
>
> include/linux/tty.h
> include/linux/tty_driver.h
> include/linux/tty_flip.h
> include/linux/tty_ldisc.h
>
> include/linux/vt_buffer.h
> include/linux/vt_kern.h
Yes, that looks good.
Can you extend the tool to include/uapi too?
For example this is missing too:
include/uapi/linux/tty*.h
It expands to:
include/uapi/linux/tty_flags.h
include/uapi/linux/tty.h
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on next-20210507
>
> MAINTAINERS | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8923f0064784..d056f777c1a5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18563,9 +18563,13 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git
> F: Documentation/driver-api/serial/
> F: drivers/tty/
> F: drivers/tty/serial/serial_core.c
> +F: include/linux/selection.h
> F: include/linux/serial.h
> F: include/linux/serial_core.h
> -F: include/linux/tty.h
> +F: include/linux/sysrq.h
> +F: include/linux/tty*.h
> +F: include/linux/vt.h
> +F: include/linux/vt_*.h
> F: include/uapi/linux/serial.h
> F: include/uapi/linux/serial_core.h
> F: include/uapi/linux/tty.h
>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2021-05-18 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 5:21 [RFC PATCH 0/1] Mining maintainers for kernel headers Lukas Bulwahn
2021-05-18 5:21 ` [RFC PATCH 1/1] MAINTAINERS: TTY LAYER: add some ./include/linux/ header files Lukas Bulwahn
2021-05-18 5:37 ` Jiri Slaby [this message]
2021-05-23 7:05 ` Lukas Bulwahn
2021-05-23 8:18 ` Greg Kroah-Hartman
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=69da627e-91c5-66f0-c0c9-75fbaaba6782@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=ralf.ramsauer@oth-regensburg.de \
/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