public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Vikram Kandukuri <Vikram.Kandukuri@Atheros.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH] DFU Driver and firmware for Atheros bluetooth chipset AR3011
Date: Tue, 17 Nov 2009 21:27:33 +0100	[thread overview]
Message-ID: <1258489653.2003.30.camel@violet> (raw)
In-Reply-To: <20091117191112.GD11382@tux>

Hi Luis,

> On Tue, Nov 17, 2009 at 06:59:00AM -0800, Marcel Holtmann wrote:
> > > +MODULE_AUTHOR("Atheros Communications");
> > > +MODULE_DESCRIPTION("Atheros AR3011 firmware driver");
> > > +MODULE_VERSION(DRV_VERSION);
> > > +MODULE_SUPPORTED_DEVICE("Atheros AR3011 chipset");
> > > +MODULE_LICENSE("GPL");
> > > +MODULE_FIRMWARE("atherosbt.bin");
> > 
> > The
> > module author needs to have a contact information and not just the
> > company name. Read it as who maintains this driver.
> 
> This is probably just following what we have on ath9k / ath9k_common / ath9k_hw / ath
> modules which so far no one has asked us to change:
> 
> MODULE_AUTHOR("Atheros Communications");
> MODULE_DESCRIPTION("Support for Atheros 802.11n wireless LAN cards.");
> MODULE_SUPPORTED_DEVICE("Atheros 802.11n WLAN cards");
> MODULE_LICENSE("Dual BSD/GPL");
> 
> Using one contact point for ath9k stuff doesn't work for us as we have a group
> and for that the MAINTAINERS file seems just suitable. Plus -- some module authors
> are sometimes not the current maintainers so the MDOULE_AUTHOR really doesn't mean
> much. Wouldn't updating the MAINTAINERS file accordingly be better?

my personal advise for the long term would be to create a mailing list
sort of contact address. As I said, the MODULE_AUTHOR is meant to
reflect the current maintainer. It is of course not a hard requirement,
but it is the intention. If you don't have that right now, we go with
this, but think about establishing something like it.

> Also Vikram -- why not just ISC license the files as we do with ath9k ? Then also
> use:
> 
> MODULE_LICENSE("Dual BSD/GPL");
> 
> This would be more consistant with what we do with our other upstream Atheros
> modules.

Since this is just a firmware loading driver, I prefer if you just keep
it GPL only. It is not worth going into too much details. Especially
since it looks inspired (nicely phrased) from bcm203x.c driver.

Regards

Marcel



  reply	other threads:[~2009-11-17 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 14:36 [PATCH] DFU Driver and firmware for Atheros bluetooth chipset AR3011 Kandukuri Vikram
2009-11-17 14:59 ` Marcel Holtmann
2009-11-17 17:45   ` Luis R. Rodriguez
2009-11-17 20:29     ` Marcel Holtmann
2009-11-17 19:11   ` Luis R. Rodriguez
2009-11-17 20:27     ` Marcel Holtmann [this message]
2009-11-17 21:47       ` David Sainty
2009-11-17 21:59         ` Luis R. Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2009-11-17 14:48 Vasanthakumar Thiagarajan
2009-11-17 14:48 Vikram Kandukuri

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=1258489653.2003.30.camel@violet \
    --to=marcel@holtmann.org \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Vikram.Kandukuri@Atheros.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    /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