From: Camaleón <noelamac@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"sgruszka@redhat.com" <sgruszka@redhat.com>,
"jrnieder@gmail.com" <jrnieder@gmail.com>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: brcmsmac still woes, possible regression?
Date: Thu, 29 Mar 2012 15:38:35 +0200 [thread overview]
Message-ID: <20120329133835.GA5196@stt008.linux.site> (raw)
In-Reply-To: <4F744DD8.8010004@broadcom.com>
El 2012-03-29 a las 13:56 +0200, Arend van Spriel escribió:
> On 03/28/2012 11:59 PM, Camaleón wrote:
>> 2012/3/28 Arend van Spriel<arend@broadcom.com>:
>>> On 03/28/2012 01:26 PM, Camaleón wrote:
>>
>>>>> Did you have any opportunity to test the patch?
(...)
>> Here it goes.
>>
>> There's another trace, so now I doubt that I have applied the patches
>> correctly... Mmm, how could check if the brcmsmac module which I have
>> compiled and loaded has the patch applied? :-?
>>
>> Greetings,
>>
>
> So you have 3.3 kernel sources. Is that from a tarball or are you using
> git? For git it would be pretty easy to verify you have the patch.
I have the sources, so I applied the patch ("patch -p1 < file.patch")
and then compiled the full kernel again. I can see the three files
(channel.c, main.c and main.h) have been modified but I'm unsure.
Greetings,
--
Camaleón
next prev parent reply other threads:[~2012-03-29 13:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 8:55 brcmsmac still woes, possible regression? Camaleón
2012-03-24 9:27 ` Arend van Spriel
2012-03-24 10:04 ` Camaleón
2012-03-24 11:21 ` Camaleón
2012-03-26 9:23 ` Arend van Spriel
2012-03-26 9:43 ` Camaleón
2012-03-26 10:10 ` Arend van Spriel
2012-03-26 21:28 ` Camaleón
2012-03-27 8:47 ` Arend van Spriel
2012-03-28 11:19 ` Arend van Spriel
2012-03-28 11:26 ` Camaleón
2012-03-28 12:23 ` Arend van Spriel
2012-03-28 21:59 ` Camaleón
2012-03-29 11:56 ` Arend van Spriel
2012-03-29 13:38 ` Camaleón [this message]
2012-04-02 13:29 ` Camaleón
2012-04-02 21:50 ` Jonathan Nieder
2012-04-03 6:25 ` Camaleón
2012-04-03 15:30 ` Arend van Spriel
2012-05-09 9:41 ` Jonathan Nieder
2012-05-09 10:23 ` Arend van Spriel
2012-05-09 10:29 ` Jonathan Nieder
2012-05-09 10:32 ` Arend van Spriel
2012-05-09 17:41 ` Seth Forshee
2012-05-09 18:01 ` Arend van Spriel
2012-05-09 18:10 ` Johannes Berg
2012-05-10 16:35 ` Seth Forshee
2012-05-11 9:32 ` Johannes Berg
2012-05-11 17:31 ` Seth Forshee
2012-05-16 20:15 ` Seth Forshee
2012-05-29 7:16 ` Johannes Berg
2012-03-26 14:32 ` Seth Forshee
2012-03-26 16:54 ` Arend van Spriel
2012-03-26 17:13 ` Seth Forshee
2012-03-26 17:15 ` Arend van Spriel
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=20120329133835.GA5196@stt008.linux.site \
--to=noelamac@gmail.com \
--cc=arend@broadcom.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=sgruszka@redhat.com \
/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.