All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
	Marek Belisko <marek.belisko@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Deepa Dinamani <deepa.kernel@gmail.com>
Subject: Re: Bad MAINTAINERS pattern in section 'STAGING - FLARION FT1000 DRIVERS'
Date: Fri, 28 Sep 2018 17:46:49 -0700	[thread overview]
Message-ID: <20180929004649.GA28840@kroah.com> (raw)
In-Reply-To: <20180928220423.31573-1-joe@perches.com>

On Fri, Sep 28, 2018 at 03:04:23PM -0700, Joe Perches wrote:
> Please fix this defect appropriately.
> 
> linux-next MAINTAINERS section:
> 
> 	13899	STAGING - FLARION FT1000 DRIVERS
> 	13900	M:	Marek Belisko <marek.belisko@gmail.com>
> 	13901	S:	Odd Fixes
> -->	13902	F:	drivers/staging/ft1000/
> 
> Commit that introduced this:
> 
> commit a0138163cfbfdfbdc20e4477c77bd7046bd66bb4
>  Author: Joe Perches <joe@perches.com>
>  Date:   Tue Jul 5 15:21:34 2011 -0700
>  
>      MAINTAINERS: Add remaining staging entries
>      
>      Add the staging entries from various TODO files
>      to MAINTAINERS.  Add a few web links as well.
>      
>      Miscellaneous staging typo section header fix.
>      
>      Signed-off-by: Joe Perches <joe@perches.com>
>      Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>  
>   MAINTAINERS | 69 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 68 insertions(+), 1 deletion(-)

So you are going to fix this, considering you created the problem?

This is an odd request to make of yourself in public, or was this a
script gone wrong?

confused,

greg k-h

  reply	other threads:[~2018-09-29  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 22:04 Bad MAINTAINERS pattern in section 'STAGING - FLARION FT1000 DRIVERS' Joe Perches
2018-09-29  0:46 ` Greg Kroah-Hartman [this message]
2018-09-29  1:15   ` Joe Perches

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=20180929004649.GA28840@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=deepa.kernel@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.belisko@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.