From: Matt Fleming <matt@codeblueprint.co.uk>
To: Joe Perches <joe@perches.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names
Date: Fri, 13 May 2016 16:34:35 +0100 [thread overview]
Message-ID: <20160513153435.GA2837@codeblueprint.co.uk> (raw)
In-Reply-To: <1463153027.14219.3.camel@perches.com>
On Fri, 13 May, at 08:23:47AM, Joe Perches wrote:
> On Fri, 2016-05-13 at 17:11 +0200, Xose Vazquez Perez wrote:
> > Matt Fleming wrote:
> >
> > >
> > > Mark reported that having asterisks on the end of directory names
> > > confuses get_maintainer.pl when it encounters subdirectories, and
> > > that
> > If this's a get_maintainer.pl bug, it should also happen in:
>
> Mark is confused.
Sorry, "confuses" was my word, not Mark's.
> The meaning of * is all the files in a particular
> directory but not any subdirectories.
Exactly. This is not what EFI maintainer entries should be using. I am
responsible for everything under drivers/firmware/efi, including
subdirectories.
next prev parent reply other threads:[~2016-05-13 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 15:11 [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names Xose Vazquez Perez
2016-05-13 15:23 ` Joe Perches
2016-05-13 15:34 ` Matt Fleming [this message]
2016-05-13 16:15 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2016-05-03 19:29 [GIT PULL 0/3] EFI urgent fixes Matt Fleming
[not found] ` <1462303781-8686-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-05-03 19:29 ` [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names Matt Fleming
2016-05-03 19:29 ` Matt Fleming
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=20160513153435.GA2837@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=xose.vazquez@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.