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:51:43 -0700	[thread overview]
Message-ID: <4C97D76F.1040601@wetwork.net> (raw)
In-Reply-To: <AANLkTim-69if8MdUtDnE+sDU0hCMUed6WGaPURCAy5W4@mail.gmail.com>

On 09/20/2010 02:33 PM, Luis R. Rodriguez wrote:
> Please avoid HTML e-mails.
>    

Luis, when I read your first post I thought "Ignore this guy" but then I 
gave you the benefit of the doubt.

Yeah absolutely no HTML.  Please avoid giving me commands when you're 
not my CO.

> On Mon, Sep 20, 2010 at 2:22 PM, Ehud Gavron<gavron@wetwork.net>  wrote:
>    
>> It is not up to us to "...deal with regulatory considerations..."
>>      
> No, you see, that's wrong because no one else was,
That isn't a sentence, and makes no sense if I try to figure out what 
you intended.
>   we started getting upstream support from companies

"We" got no such thing.

> only once we found decent solutions for regulatory.

I think there's a noun missing from there, baby.

> So as much as you want to bark
Woof woof, baby.
>   that we don't need to deal with them I can already prove to you that you were wrong.
I "were" wrong?  Cool.   So now I'm not.  Cool.  Thanks.

> If you don't you simply don't get support, if you do, then you accelerate the
> pace of adoption for Linux. One way or another the changes have to
> happen, how you manage to get the changes done will highly affect how
> soon you'll get support.
>    

Yeah.  Like my older brothers used to say: It's time for you to go to bed.

E
>    
>> The "best we can do" is code, and that's what coders do.  The lawyers can do what lawyers do.*
>>      
> And what do you want to code? Piece of shit reverse engineered quality
> code? I guarantee you if you get proper vendor support the quality of
> the drivers improves considerably.
>
>    
>> and we're ahead of others because we're not wasting our time on legal crap.
>>      
> No, we are ahead because we envision the path to enhancing radio
> capabilities and dynamic communication. The regulatory solutions in
> place in Linux help with regulatory considerations but as a side
> effect it also paves the way for next generation radio technologies.
>
>    Luis
>    

-- 

-------------- 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/b9a7ebf7/attachment.p7s>

  reply	other threads:[~2010-09-20 21:51 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
2010-09-20 21:33           ` Luis R. Rodriguez
2010-09-20 21:51             ` Ehud Gavron [this message]
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=4C97D76F.1040601@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.