All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: unexpected taint message
Date: Fri, 16 Dec 2011 15:00:41 +0100	[thread overview]
Message-ID: <4EEB4F09.6080806@broadcom.com> (raw)
In-Reply-To: <4EEB4D61.80602@lwfinger.net>

On 12/16/2011 02:53 PM, Larry Finger wrote:
> 
> I also found that loading brcmsmac did not trigger the license taint. I think 
> you are OK with the dual license.

Ok. I get it upon loading the brcmutil module. Actually, my usage
scenario is:

1) build the driver modules in kernel tree on my development machine.
2) rsync the brcm80211 folder to my test machine.
3) insert the driver modules on my test machine.

> Larry
> 

Gr. AvS


      parent reply	other threads:[~2011-12-16 14:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  9:27 unexpected taint message Arend van Spriel
2011-12-16  9:29 ` Daniel Baluta
2011-12-16 10:03   ` Arend van Spriel
2011-12-16 12:30 ` Johannes Berg
2011-12-16 13:53   ` Larry Finger
2011-12-16 13:58     ` Johannes Berg
2011-12-16 14:13       ` Larry Finger
2011-12-16 14:20         ` Johannes Berg
2011-12-16 14:49           ` Larry Finger
2011-12-16 14:51             ` Johannes Berg
2011-12-16 14:48       ` Nick Bowler
2011-12-16 14:57         ` Larry Finger
2011-12-16 14:58         ` Johannes Berg
2011-12-16 14:00     ` Arend van Spriel [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=4EEB4F09.6080806@broadcom.com \
    --to=arend@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.