From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
"Josh Boyer" <jwboyer@redhat.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 13:39:10 +0200 [thread overview]
Message-ID: <501A66DE.3000500@broadcom.com> (raw)
In-Reply-To: <1343854723-21987-1-git-send-email-seth.forshee@canonical.com>
On 08/01/2012 10:58 PM, Seth Forshee wrote:
> Seth Forshee (2):
> cfg80211: add channel flag to restrict OFDM
> brcmsmac: use channel flags to restrict OFDM
>
> drivers/net/wireless/brcm80211/brcmsmac/channel.c | 5 +----
> .../net/wireless/brcm80211/brcmsmac/mac80211_if.c | 3 ++-
> include/net/cfg80211.h | 2 ++
> net/wireless/reg.c | 2 ++
> 4 files changed, 7 insertions(+), 5 deletions(-)
Does the trick. No more warnings on lockdep kernel. For both you can add
Tested-by: Arend van Spriel <arend@broadcom.com>
Gr. AvS
prev parent reply other threads:[~2012-08-02 11:39 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
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 [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=501A66DE.3000500@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.