linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: [RFT 6/6] carl9170usb: Makefile, Kconfig files and MAINTAINERS
Date: Tue, 31 Aug 2010 01:20:59 +0200	[thread overview]
Message-ID: <201008310121.00085.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTinXJN7q3CXLVxNP=S2fGQHQJxLEmwvbAV17+Q_i@mail.gmail.com>

On Tuesday 31 August 2010 00:45:42 Julian Calaby wrote:
> On Tue, Aug 31, 2010 at 06:42, Christian Lamparter
> <chunkeey@googlemail.com> wrote:
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 63e441b..1f10089 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1119,6 +1119,7 @@ L:        linux-wireless@vger.kernel.org
> >  W:     http://wireless.kernel.org/en/users/Drivers/ar9170
> >  S:     Maintained
> >  F:     drivers/net/wireless/ath/ar9170/
> > +F:     drivers/net/wireless/ath/carl9170/
> >
> >  ATK0110 HWMON DRIVER
> >  M:     Luca Tettamanti <kronos.it@gmail.com>
> 
> As carl9170 has a separate website, would it make sense for it to also
> have a separate MAINTAINERS entry?
On one hand the driver is based on ar9170 and uses the same device,
but having an separate entry might be favorable when ar9170usb is
dropped...

> Also, patch 1/6 is signed off by root, you may want to fix that.
Thanks!

---

By the way:

ALL COMPAT-WIRELESS USERS WITH OLDER KERNELS (older than 2.6.36-rc1, 2.6.35.2,
etc...) have to apply this patch:
> https://patchwork.kernel.org/patch/118946/
(Or, suffer from panics.)

      reply	other threads:[~2010-08-30 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30 20:42 [RFT 6/6] carl9170usb: Makefile, Kconfig files and MAINTAINERS Christian Lamparter
2010-08-30 22:45 ` Julian Calaby
2010-08-30 23:20   ` Christian Lamparter [this message]

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=201008310121.00085.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).