From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
"Pavel Machek" <pavel@suse.cz>,
"Uwe Kleine-König" <ukleinek@strlen.de>
Subject: Re: [PATCH 1/3] Add file patterns to MAINTAINERS
Date: Tue, 21 Oct 2008 01:45:53 +0200 [thread overview]
Message-ID: <20081020234553.GA13115@isilmar.linta.de> (raw)
In-Reply-To: <1224543747.12101.66.camel@localhost>
On Mon, Oct 20, 2008 at 04:02:26PM -0700, Joe Perches wrote:
> On Tue, 2008-10-21 at 00:50 +0200, Dominik Brodowski wrote:
> > Hi,
> >
> > > PCMCIA SUBSYSTEM
> > > P: Linux PCMCIA Team
> > > L: linux-pcmcia@lists.infradead.org
> > > W: http://lists.infradead.org/mailman/listinfo/linux-pcmcia
> > > T: git kernel.org:/pub/scm/linux/kernel/git/brodo/pcmcia-2.6.git
> > > S: Maintained
> > > +F: Documentation/pcmcia/
> > > +F: drivers/*/pcmcia/
> > > +F: drivers/pcmcia/
> > > +F: include/pcmcia/
> > > +F: sound/pcmcia/
> >
> > sound/pcmcia/ and lots of drivers/*/pcmcia is actually really
> > driver-related and not PCMCIA related so I'm not really happy if this will
> > be described by the PCMCIA F:-realm...
>
> I generated that pattern from patchsets like:
> http://lists.infradead.org/pipermail/linux-pcmcia/2008-August/005787.html
Yes, that's PCMCIA infrastructure work.
> If you could send a more correct pattern,
> it's easy to change.
Well, there are mostly four areas, which, in my opinion, should be solved
like this:
sound/pcmcia/ should be under SOUND
drivers/net/pcmcia/ should be under NETWORK DEVICE DRIVERS
drivers/scsi/pcmcia/ should be under SCSI SUBSYSTEM
and
drivers/char/pcmcia/cm4000_cs.c OMNIKEY CARDMAN 4000 DRIVER
drivers/char/pcmcia/cm4040_cs.c OMNIKEY CARDMAN 4040 DRIVER
and finally
drivers/char/pcmcia/ipwireess/* IPWIRELESS DRIVER
Thanks!
Dominik
next prev parent reply other threads:[~2008-10-20 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 22:28 [PATCH 0/3] Add file patterns to MAINTAINERS and script to parse MAINTAINERS Joe Perches
2008-10-20 22:28 ` [PATCH 1/3] Add file patterns to MAINTAINERS Joe Perches
2008-10-20 22:28 ` [PATCH 2/3] Add a script to parse file pattern information in MAINTAINERS Joe Perches
2008-10-20 22:28 ` [PATCH 3/3] MAINTAINERS updates Joe Perches
2008-10-21 8:26 ` Pavel Machek
2008-10-21 8:31 ` Joe Perches
2008-10-20 22:50 ` [PATCH 1/3] Add file patterns to MAINTAINERS Dominik Brodowski
2008-10-20 23:02 ` Joe Perches
2008-10-20 23:45 ` Dominik Brodowski [this message]
2008-10-21 0:12 ` Joe Perches
2008-10-21 0:30 ` Dominik Brodowski
2008-10-21 1:58 ` Jeff Kirsher
2008-10-21 2:38 ` Joe Perches
2008-10-21 8:25 ` Pavel Machek
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=20081020234553.GA13115@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=ukleinek@strlen.de \
/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
Powered by JetHome