public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
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: Mon, 20 Oct 2008 17:12:58 -0700	[thread overview]
Message-ID: <1224547979.12101.90.camel@localhost> (raw)
In-Reply-To: <20081020234553.GA13115@isilmar.linta.de>

On Tue, 2008-10-21 at 01:45 +0200, Dominik Brodowski wrote:
> On Mon, Oct 20, 2008 at 04:02:26PM -0700, Joe Perches wrote:
> > If you could send a more correct pattern,
> > it's easy to change.

Would you keep any PCMCIA pattern?

Perhaps:
F:	Documentation/pcmcia/
F:	include/pcmcia/
F:	drivers/pcmcia/cs*
F:	drivers/pcmcia/pcmcia*
F:	drivers/pcmcia/rsrc*

This should cover the core utilities and leave 
drivers that use pcmcia services out.

> 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
> drivers/char/pcmcia/cm4000_cs.c			OMNIKEY CARDMAN 4000 DRIVER
> drivers/char/pcmcia/cm4040_cs.c			OMNIKEY CARDMAN 4040 DRIVER

File patterns for these sections are setup as you suggested.

> and finally
> drivers/char/pcmcia/ipwireess/*			IPWIRELESS DRIVER

I didn't have a pattern for that section, thanks.

Also, file patterns are not exclusive.
A pattern may exist in more than 1 section.
A pattern with a trailing / includes all subdirectories.

cheers, Joe


  reply	other threads:[~2008-10-21  0:13 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
2008-10-21  0:12         ` Joe Perches [this message]
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=1224547979.12101.90.camel@localhost \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --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