From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/18] MAINTAINERS: Remove IEEE1394 entry
Date: Wed, 23 Feb 2011 08:57:14 +0100 [thread overview]
Message-ID: <20110223085714.3be20a36@stein> (raw)
In-Reply-To: <521a178e6e611d444adf2b49c20ee5ba67e7c6b7.1298439175.git.joe@perches.com>
On Feb 22 Joe Perches wrote:
> commit 66fa12c571d35e3cd62574c65f1785a460105397
> ("ieee1394: remove the old IEEE 1394 driver stack")
>
> removed the code, remove the MAINTAINERS entry.
[...]
Indeed, thanks.
--
Stefan Richter
-=====-==-== --=- =-===
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-02-23 7:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 5:41 [PATCH 00/18] MAINTAINERS: Trivial corrections Joe Perches
2011-02-23 5:41 ` [PATCH 01/18] MAINTAINERS: Update ADP5520 pattern Joe Perches
2011-02-23 8:54 ` Hennerich, Michael
2011-02-23 5:41 ` [PATCH 02/18] MAINTAINERS: Change web links from wiki-analog to wiki.analog Joe Perches
2011-02-23 6:17 ` Mike Frysinger
2011-02-23 5:41 ` [PATCH 03/18] MAINTAINERS: Remove ASOC CODEC DRIVERS files not in tree Joe Perches
2011-02-23 5:41 ` [PATCH 04/18] MAINTAINERS: Add missing : after HR Timers F tag Joe Perches
2011-02-23 9:44 ` Harry Wei
2011-02-23 5:41 ` [PATCH 05/18] MAINTAINERS: Remove unnecessary linux-kernel@vger.kernel.org entries Joe Perches
2011-02-23 9:43 ` Harry Wei
2011-03-01 11:20 ` Mark Brown
2011-03-01 11:53 ` Joe Perches
2011-03-01 11:57 ` Mark Brown
2011-03-01 12:24 ` Joe Perches
2011-03-01 12:26 ` Mark Brown
2011-03-01 14:10 ` Harry Wei
2011-03-01 14:13 ` Mark Brown
[not found] ` <AANLkTin2++GT3eRcTQeeqcB_1whedAt_0Hn+YY8y=v1s@mail.gmail.com>
2011-03-01 14:47 ` Fwd: " Harry Wei
2011-03-08 19:45 ` Steven Rostedt
2011-03-10 2:07 ` Harry Wei
2011-02-23 5:41 ` [PATCH 06/18] MAINTAINERS: Update clkdev location Joe Perches
2011-02-23 6:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-02-23 5:42 ` [PATCH 07/18] MAINTAINERS: Update media path Joe Perches
2011-02-23 9:46 ` Harry Wei
2011-02-23 5:42 ` [PATCH 08/18] MAINTAINERS: Update HVC file patterns Joe Perches
2011-02-23 5:42 ` [PATCH 09/18] MAINTAINERS: Quote non-alphanumeric email addresses Joe Perches
2011-02-23 9:48 ` Harry Wei
2011-02-23 5:42 ` [PATCH 10/18] MAINTAINERS: Remove unused clockevents.h Joe Perches
2011-02-23 5:42 ` [PATCH 11/18] MAINTAINERS: Remove IEEE1394 entry Joe Perches
2011-02-23 7:57 ` Stefan Richter [this message]
2011-02-23 5:42 ` [PATCH 12/18] MAINTAINERS: Remove unused TIMEKEEPING timekeeping.h Joe Perches
2011-02-23 5:42 ` [PATCH 13/18] MAINTAINERS: Update SCX200 file pattern Joe Perches
2011-02-23 5:42 ` [PATCH 14/18] MAINTAINERS: Remove SHARP LH7A40X section Joe Perches
2011-02-23 5:42 ` [PATCH 15/18] MAINTAINERS: Update SFI pattern Joe Perches
2011-02-23 5:42 ` [PATCH 16/18] MAINTAINERS: Update TIPC patterns Joe Perches
2011-02-23 5:42 ` [PATCH 17/18] MAINTAINERS: USB SE401 moved to staging, update pattern Joe Perches
2011-02-23 10:45 ` Mauro Carvalho Chehab
2011-02-23 5:42 ` [PATCH 18/18] MAINTAINERS: Update WINBOND CIR pattern Joe Perches
2011-02-23 10:45 ` Mauro Carvalho Chehab
2011-02-23 15:39 ` David Härdeman
2011-02-23 9:40 ` [PATCH 00/18] MAINTAINERS: Trivial corrections Harry Wei
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=20110223085714.3be20a36@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@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