public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
	netdev@vger.kernel.org, linux-pcmcia@lists.infradead.org,
	David Miller <davem@davemloft.net>
Subject: MAINTAINERS: PCMCIA SUBSYSTEM: Should F: drivers/net/pcmcia/ be added?
Date: Thu, 12 Aug 2010 15:47:52 -0700	[thread overview]
Message-ID: <1281653272.15486.62.camel@Joe-Laptop> (raw)
In-Reply-To: <1281651771.15486.55.camel@Joe-Laptop>

On Thu, 2010-08-12 at 15:22 -0700, Joe Perches wrote:
> On Mon, 2010-08-09 at 17:34 +0200, Dominik Brodowski wrote:
> > look good from a PCMCIA point of view, therefore:
> > Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>

There's no maintainer entry for directory drivers/net/pcmcia/

Should

F:	drivers/net/pcmcia/

be added to the existing PCMCIA SUBSYSTEM entry?





  reply	other threads:[~2010-08-12 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 12:32 [PATCH] pcnet_cs: Use proper netdev_*-printouts Wolfram Sang
2010-08-08 14:50 ` [PATCH] pcnet_cs: Use pr_fmt and pr_<level> Joe Perches
2010-08-17  9:34   ` David Miller
2010-08-09 15:34 ` [PATCH] pcnet_cs: Use proper netdev_*-printouts Dominik Brodowski
2010-08-12 22:22   ` [PATCH net-next 2.6.37?] drivers/net/pcmcia: Use pr_<level> and netdev_<level> Joe Perches
2010-08-12 22:47     ` Joe Perches [this message]
2010-08-13 18:52       ` MAINTAINERS: PCMCIA SUBSYSTEM: Should F: drivers/net/pcmcia/ be added? Dominik Brodowski
2010-08-13 18:51     ` [PATCH net-next 2.6.37?] drivers/net/pcmcia: Use pr_<level> and netdev_<level> Dominik Brodowski
2010-08-18 21:27     ` David Miller
2010-08-17  9:34 ` [PATCH] pcnet_cs: Use proper netdev_*-printouts David Miller

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=1281653272.15486.62.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=davem@davemloft.net \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linux@dominikbrodowski.net \
    --cc=netdev@vger.kernel.org \
    --cc=w.sang@pengutronix.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