From: Joe Perches <joe@perches.com>
To: Ingo Molnar <mingo@elte.hu>
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, 02 Jun 2011 01:26:07 -0700 [thread overview]
Message-ID: <1307003167.32125.59.camel@Joe-Laptop> (raw)
In-Reply-To: <20110602074057.GE2150@elte.hu>
On Thu, 2011-06-02 at 09:40 +0200, Ingo Molnar wrote:
> * Joe Perches <joe@perches.com> wrote:
> > No arch/*/lib/perf_event* files exist so remove the pattern.
> The arch/*/lib/ hierarchy is a common place to put stuff into, it
> does not hurt at all to have it mentioned.
Every once in awhile I run a script on MAINTAINERS
and fix up defects found by the script.
Dead code is dead code.
This was unused as of commit e360adbe2924.
> stop mucking with these patterns and start dealing
> with some of the more important problems we have?
My time, my choice on what to do with it.
next prev parent reply other threads:[~2011-06-02 8:26 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
2011-06-02 8:26 ` Joe Perches [this message]
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=1307003167.32125.59.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.