mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vic" <kernel@beer.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: RTL2831U kernel driver
Date: Thu, 22 Nov 2007 15:44:54 -0000 (GMT)	[thread overview]
Message-ID: <41536.127.0.0.1.1195746294.squirrel@127.0.0.1> (raw)
In-Reply-To: <20071122141713.79f2562a@the-village.bc.nu>

> That would depend who wrote it.
>
> If they wrote it then yes it would be good to add that information and
> the GPLv3 and a note about the email permission to release.

They wrote it.

> Either way it would be good if a copy of the agreement email went
> (privately) to the Linux Foundation so its on record should there ever be
> questions, and possibly to Linus as well.

Well that's just fine - anyone care to tell me how to do that :-) I've
never been in this sort of position before...

> And thanks appear in order to Realtek.

Well yes. I've thanked them - but I'd also like to see them get some
community recognition. I see this as an important step...

> Wouldn't it possible to ask them to release it themselves to the lkml
> with proper attribution (and, as they see fit, with or without support) ?

I don't think it'd be wise to go down that path; I didn't even manage to
get a datasheet out of them (which is how this all started). They've sent
me the code, they've given permission to release it under the GPL - let's
just get on with disseminating it.

So - how to I submit it?

Vic.




  parent reply	other threads:[~2007-11-22 15:45 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 [this message]
2007-11-22 16:01     ` Alan Cox
2007-11-22 18:11 ` Mauro Carvalho Chehab
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=41536.127.0.0.1.1195746294.squirrel@127.0.0.1 \
    --to=kernel@beer.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®