mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: kernel@beer.org.uk
Cc: linux-kernel@vger.kernel.org,
	v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: RTL2831U kernel driver
Date: Thu, 22 Nov 2007 16:11:21 -0200	[thread overview]
Message-ID: <1195755081.4810.23.camel@gaivota> (raw)
In-Reply-To: <40711.127.0.0.1.1195734828.squirrel@127.0.0.1>

Em Qui, 2007-11-22 às 12:33 +0000, Vic escreveu:
> Hi All.
> 
> Sorry for the breach of netiquette - I'm not subscribed to the list
> (please CC: me on anything important!), but I'm not really up to much a s
> a kernel contributor...
> 
> Anyway - here's the reason for my posting. I've got a kernel driver for
> the RTL2831U device (a DVB-T device) from Realtek. Just this morning, I
> got an email from them agreeing to release it under GPL.
> 
> It currently has no copright notices at all

Kernel is GPLv2. So, the driver should be released under GPLv2 only or
GPLv2 or later.

>  - I think I should add Realtek attributions to it.

I would be better if someone from Realtek could send the driver. Anyway,
any driver submitted to kernel should be signed with a SOB. 

There's a guide on how to submit a driver to kernel. For convenience,
they are briefly summarized at
http://linuxtv.org/v4lwiki/index.php/How_to_submit_patches

> Then what should I do?

It would be nice if you can subscribe to Linux DVB mailing [1] list and
post the driver there. The list is open to users and to developers, so,
maybe it would be interesting for you to participate there.

[1] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

If you are not willing to subscribe to DVB ML, please copy V4L/DVB
maintainers mailing list[2] on this subject. This list allows you to
post even not being a subscriber.

[2] v4l-dvb-maintainer@linuxtv.org

It is important to submit the driver either to DVB or V4L/DVB
maintainers ML, since this will allow all developers to take a look at
the driver, checking for eventual issues, and helping to improve it.
Several developers are not subscribed to LKML (or don't read it
regularly).
 
Cheers,
Mauro


  parent reply	other threads:[~2007-11-22 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22 12:33 Vic
2007-11-22 14:17 ` Alan Cox
2007-11-22 14:47   ` Alan Cox
2007-11-22 15:44   ` Vic
2007-11-22 16:01     ` Alan Cox
2007-11-22 18:11 ` Mauro Carvalho Chehab [this message]
2007-11-22 15:32 Loïc Grenié

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=1195755081.4810.23.camel@gaivota \
    --to=mchehab@infradead.org \
    --cc=kernel@beer.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.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

all inboxes | Powered by JetHome®