From: Lucas Kannebley Tavares <lucaskt@linux.vnet.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Subject: Re: [PATCH] Updated TTY MAINTAINERS info
Date: Mon, 09 Jan 2012 18:34:46 -0200 [thread overview]
Message-ID: <4F0B4F66.8000302@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120109200751.GA8337@suse.de>
On 01/09/2012 06:07 PM, Greg KH wrote:
> On Mon, Jan 09, 2012 at 05:39:24PM -0200, Lucas Kannebley Tavares wrote:
>> Greg Kroah-Hartman is the current TTY maintainer, however he wouldn't appear
>> listed as such upon running get_maintainers.pl for drivers under
>> drivers/tty/serial.
>>
>> Signed-off-by: Lucas Kannebley Tavares<lucaskt@linux.vnet.ibm.com>
>> ---
>> MAINTAINERS | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index cc6a466..6a856df 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -6641,7 +6641,7 @@ TTY LAYER
>> M: Greg Kroah-Hartman<gregkh@suse.de>
>> S: Maintained
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6.git
>> -F: drivers/tty/*
>> +F: drivers/tty/
>
> Isn't this just a bug in the get_maintainers.pl script? Why does this
> patch fix the problem?
>
> greg k-h
>
To quote from MAINTAINERS
> F: Files and directories with wildcard patterns.
> A trailing slash includes all files and subdirectory files.
> F: drivers/net/ all files in and below drivers/net
> F: drivers/net/* all files in drivers/net, but not below
In this case I believe you are the maintainer for the entire tree, or am
I mistaken? If so, the documentation states that it shouldn't have an
asterisk.
Lucas
next prev parent reply other threads:[~2012-01-09 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 19:39 [PATCH] Updated TTY MAINTAINERS info Lucas Kannebley Tavares
2012-01-09 20:07 ` Greg KH
2012-01-09 20:34 ` Lucas Kannebley Tavares [this message]
2012-01-09 22:52 ` Greg KH
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=4F0B4F66.8000302@linux.vnet.ibm.com \
--to=lucaskt@linux.vnet.ibm.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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