All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 4/6] MAINTAINERS: Remove unused PERFORMANCE EVENTS pattern
Date: Thu, 2 Jun 2011 09:40:57 +0200	[thread overview]
Message-ID: <20110602074057.GE2150@elte.hu> (raw)
In-Reply-To: <8d1e596980a6b6fec79432bb5a5953985cf85c2f.1306950701.git.joe@perches.com>


* Joe Perches <joe@perches.com> wrote:

> No arch/*/lib/perf_event* files exist so remove the pattern.
> 
> cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> cc: Paul Mackerras <paulus@samba.org>
> cc: Ingo Molnar <mingo@elte.hu>
> cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  MAINTAINERS |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ab6340f..6f6a8ef 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4908,7 +4908,6 @@ F:	arch/*/kernel/perf_event*.c
>  F:	arch/*/kernel/*/perf_event*.c
>  F:	arch/*/kernel/*/*/perf_event*.c
>  F:	arch/*/include/asm/perf_event.h
> -F:	arch/*/lib/perf_event*.c
>  F:	arch/*/kernel/perf_callchain.c
>  F:	tools/perf/

The arch/*/lib/ hierarchy is a common place to put stuff into, it 
does not hurt at all to have it mentioned.

In Linux there's 10+ really important, not yet implemented features 
to implement, there's 100+ under-maintained subsystems to maintain, 
there's 1000+ not yet fixed bugs to fix, there's 10,000+ ugly driver 
files to be improved and there's 1,000,000+ stylistic errors to fix.

Mucking with the MAINTAINERS file on the level you did in this patch 
comes some time after we've fixed the 1,000,000+ stylistic errors.

Could you please stop mucking with these patterns and start dealing 
with some of the more important problems we have?

Thanks,

	Ingo

  reply	other threads:[~2011-06-02  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 17:59 [PATCH 0/6] MAINTAINERS: Update patterns Joe Perches
2011-06-01 17:59 ` [PATCH 1/6] MAINTAINERS: Update MSM pattern Joe Perches
2011-06-01 21:54   ` David Brown
2011-06-02 17:23     ` Carl Vanderlip
2011-06-01 17:59 ` [PATCH 2/6] MAINTAINERS: Update CPU FREQUENCY patterns Joe Perches
2011-06-01 17:59 ` [PATCH 3/6] MAINTAINERS: Update HIGH RESOLUTION TIMERS patterns Joe Perches
2011-06-01 17:59 ` [PATCH 4/6] MAINTAINERS: Remove unused PERFORMANCE EVENTS pattern Joe Perches
2011-06-02  7:40   ` Ingo Molnar [this message]
2011-06-02  8:26     ` Joe Perches
2011-06-02  9:05       ` Ingo Molnar
2011-06-01 17:59 ` [PATCH 5/6] MAINTAINERS: Update USB HID/HIDBP DRIVERS pattern Joe Perches
2011-06-07 14:03   ` Jiri Kosina
2011-06-01 17:59 ` [PATCH 6/6] MAINTAINERS: Remove section USB SE401 DRIVER 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=20110602074057.GE2150@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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 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.