All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ehud Gavron <gavron@wetwork.net>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43/b43legacy - Credit Broadcom with enabling the development of the drivers
Date: Mon, 20 Sep 2010 14:22:58 -0700	[thread overview]
Message-ID: <4C97D0B2.9080704@wetwork.net> (raw)
In-Reply-To: <AANLkTinEY2XeoA1WN8GRTdAcSebe+LUb-N9u7-zz_bpe@mail.gmail.com>



On 09/20/2010 12:09 PM, Luis R. Rodriguez wrote:
...trimmed
> That's exactly the problem, no one had the business motivation to
> really try to solve how to really deal with regulatory considerations
> with FOSS, and average developers simply wanted a solution. Its easier
> said than done. If you deal with regulatory considerations as a
> community effort then a path becomes clearer as to how to deal with
> these issues. The reason why current legislation doesn't seem to make
> sense is because it does not, but just because a law doesn't make
> sense it does not enable vendors to ignore it. So the best you can do
> in the meantime is really be proactive by working on real technical
> solutions.
>
>    

It is not up to us to "...deal with regulatory considerations..."

The "best we can do" is code, and that's what coders do.  The lawyers 
can do what lawyers do.*

> We are not dealing with legal issues on Linux, we are dealing with
> engineering solutions, and trust me, we're light years ahead of other
> OSes because of this now.
>
>    Luis
>    
Light year is a measure of distance.  You mean "years"... and we're 
ahead of others because
we're not wasting our time on legal crap.

Let the lawyers do that.

E
* Disclosures: I am not a lawyer.  I haven't coded in months. I used to 
do VMS kernel code.
-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100920/a7bd8119/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ehudwetworkcontactqrcode.png
Type: image/png
Size: 1007 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100920/a7bd8119/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5507 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100920/a7bd8119/attachment.p7s>

  reply	other threads:[~2010-09-20 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 18:40 [PATCH] b43/b43legacy - Credit Broadcom with enabling the development of the drivers David Woodhouse
2010-09-20 16:36 ` Gábor Stefanik
2010-09-20 16:36   ` Gábor Stefanik
2010-09-20 16:56   ` Luis R. Rodriguez
2010-09-20 16:56     ` Luis R. Rodriguez
2010-09-20 19:02     ` Ehud Gavron
2010-09-20 19:09       ` Luis R. Rodriguez
2010-09-20 21:22         ` Ehud Gavron [this message]
2010-09-20 21:33           ` Luis R. Rodriguez
2010-09-20 21:51             ` Ehud Gavron
2010-09-21  4:01               ` Peter Stuge
2010-09-21  4:24                 ` Baybal Ni
2010-09-21  4:44                   ` Peter Stuge
2010-09-21 22:38                   ` Larry Finger
2010-09-22  5:05                     ` Michael Büsch
2010-09-22 11:14                       ` David Woodhouse
2010-09-22 17:26                         ` Luis R. Rodriguez
2010-09-22 11:07                     ` David Woodhouse
2010-09-23 19:33     ` Ealdwulf Wuffinga
2010-09-20 21:42   ` David Woodhouse
2010-09-20 21:42     ` David Woodhouse

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=4C97D0B2.9080704@wetwork.net \
    --to=gavron@wetwork.net \
    --cc=b43-dev@lists.infradead.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.