From: "John W. Linville" <linville@tuxdriver.com>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: kernel@fomichev.me, Greg Korah-Hartman <gregkh@suse.de>,
devel@linuxdriverproject.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
Arend Van Spriel <arend@broadcom.com>
Subject: Re: [PATCH v2 1/4] brcm80211: fix compile issue
Date: Tue, 15 Feb 2011 20:50:40 -0500 [thread overview]
Message-ID: <20110216015040.GA2349@tuxdriver.com> (raw)
In-Reply-To: <4D5B0034.3090303@broadcom.com>
On Tue, Feb 15, 2011 at 02:37:40PM -0800, Henry Ptasinski wrote:
> On 02/15/2011 02:12 PM, Stanislav Fomichev wrote:
> >Commit 59eb21a65047 "cfg80211: Extend channel to frequency mapping for 802.11j"
> >changed the definition of the ieee80211_channel_to_frequency; so fix its
> >usage in brcmfmac.
> >
>
> Commit 59eb21a65047 went into wireless-next a few weeks ago, but
> hasn't made it over to staging-next yet. Should John pick up this
> patch for wireless-next now, and it'll eventually migrate over to
> staging-next?
If so, not only let me know but also resend a copy to me -- I haven't
been tracking these...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-02-16 1:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1297721111-20606-1-git-send-email-kernel@fomichev.me>
[not found] ` <7A94256FD72B884D9E7C55586C3CBCEE13CDA25D88@SJEXCHCCR01.corp.ad.broadcom.com>
[not found] ` <20110215221200.GA2087@sdf-MacBook>
2011-02-15 22:37 ` [PATCH v2 1/4] brcm80211: fix compile issue Henry Ptasinski
2011-02-16 1:50 ` John W. Linville [this message]
2011-02-18 2:46 ` Henry Ptasinski
2011-02-18 3:05 ` Greg KH
2011-02-18 5:29 ` Subject: [PATCH v3] wireless-next-2.6: " Henry Ptasinski
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=20110216015040.GA2349@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=henryp@broadcom.com \
--cc=kernel@fomichev.me \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).