From: Adrian Bunk <bunk@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
"Antonino A. Daplas" <adaplas@gmail.com>,
linux-kernel@vger.kernel.org, Dave Airlie <airlied@linux.ie>
Subject: Re: Bad addresses in MAINTAINERS
Date: Tue, 14 Aug 2007 15:13:40 +0200 [thread overview]
Message-ID: <20070814131340.GO18945@stusta.de> (raw)
In-Reply-To: <1187059613.10249.372.camel@localhost>
On Mon, Aug 13, 2007 at 07:46:53PM -0700, Joe Perches wrote:
> On Tue, 2007-08-14 at 11:21 +0900, Paul Mundt wrote:
> > I also haven't had one of these devices in years, though I never got
> > around to updating MAINTAINERS. Perhaps this should be orphaned?
>
> IMS TWINTURBO FRAMEBUFFER DRIVER
> L: linux-fbdev-devel@lists.sourceforge.net (subscribers-only)
> S: Orphan
> F: drivers/video/imsttfb.c
I don't see any value in such entries:
In several areas of the kernel drivers without a driver maintainer are
the common case, and e.g. in this case the susbsystem entry for
drivers/video/ should already cover it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-08-14 13:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 19:07 Bad addresses in MAINTAINERS Joe Perches
2007-08-13 19:10 ` Mike Frysinger
2007-08-13 19:19 ` Joe Perches
2007-08-13 19:56 ` Mike Frysinger
2007-08-14 3:54 ` Robin Getz
2007-08-14 4:11 ` Mike Frysinger
2007-08-14 4:12 ` Bryan Wu
2007-08-14 4:17 ` Joe Perches
2007-08-14 4:58 ` Mike Frysinger
2007-08-14 9:59 ` Alan Cox
2007-08-14 13:09 ` Mike Frysinger
2007-08-13 19:24 ` Adrian Bunk
2007-08-13 19:42 ` Joe Perches
2007-08-14 4:18 ` Len Brown
2007-08-13 20:27 ` Antonino A. Daplas
2007-08-14 2:21 ` Paul Mundt
2007-08-14 2:46 ` Joe Perches
2007-08-14 13:13 ` Adrian Bunk [this message]
2007-08-13 20:56 ` Alan Cox
2007-08-14 12:09 ` Maciej W. Rozycki
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=20070814131340.GO18945@stusta.de \
--to=bunk@kernel.org \
--cc=adaplas@gmail.com \
--cc=airlied@linux.ie \
--cc=joe@perches.com \
--cc=lethal@linux-sh.org \
--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 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.