From: "Arend van Spriel" <arend@broadcom.com>
To: "Josh Boyer" <jwboyer@redhat.com>
Cc: "Seth Forshee" <seth.forshee@canonical.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH 0/2] Fix lockdep warning in brcmsmac
Date: Thu, 2 Aug 2012 15:42:07 +0200 [thread overview]
Message-ID: <501A83AF.9060706@broadcom.com> (raw)
In-Reply-To: <20120802125102.GF1785@zod.bos.redhat.com>
On 08/02/2012 02:51 PM, Josh Boyer wrote:
> That didn't help. I've tried multiple module load orderings without
> anything being shown on the bcma bus. The modules all load, but no
> devices are created. It's as if the hardware was removed or something.
> Puzzling.
>
> josh
Can you share the kerne configuration?
Gr. AvS
next prev parent reply other threads:[~2012-08-02 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 20:58 [PATCH 0/2] Fix lockdep warning in brcmsmac Seth Forshee
2012-08-01 20:58 ` [PATCH 1/2] cfg80211: add channel flag to prohibit OFDM operation Seth Forshee
2012-08-01 21:20 ` Luis R. Rodriguez
2012-08-02 6:24 ` Johannes Berg
2012-08-02 13:04 ` Seth Forshee
2012-08-02 13:31 ` Johannes Berg
2012-08-01 20:58 ` [PATCH 2/2] brcmsmac: use channel flags to restrict OFDM Seth Forshee
2012-08-02 0:23 ` [PATCH 0/2] Fix lockdep warning in brcmsmac Josh Boyer
2012-08-02 1:53 ` Seth Forshee
2012-08-02 12:02 ` Josh Boyer
2012-08-02 12:51 ` Josh Boyer
2012-08-02 13:42 ` Arend van Spriel [this message]
2012-08-02 13:45 ` Josh Boyer
2012-08-02 14:00 ` Arend van Spriel
2012-08-02 14:45 ` Josh Boyer
2012-08-02 14:49 ` Josh Boyer
2012-08-02 13:44 ` Hauke Mehrtens
2012-08-02 13:54 ` Josh Boyer
2012-08-02 11:01 ` Arend van Spriel
2012-08-02 11:39 ` 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=501A83AF.9060706@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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.