From: "John W. Linville" <linville@tuxdriver.com>
To: Joe Perches <joe@perches.com>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
orinoco-users@lists.sourceforge.net,
orinoco-devel@lists.sourceforge.net, netdev@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] wireless: Make and use const struct ieee80211_channel
Date: Fri, 6 May 2011 09:19:22 -0400 [thread overview]
Message-ID: <20110506131922.GA2252@tuxdriver.com> (raw)
In-Reply-To: <1304634107.1788.171.camel@Joe-Laptop>
On Thu, May 05, 2011 at 03:21:47PM -0700, Joe Perches wrote:
> On Thu, 2011-05-05 at 14:49 -0400, John W. Linville wrote:
> > These patches generated a lot of warnings in net/mac80211. Did you
> > actually build them?
>
> Yes.
>
> Did you apply patch 1/2 first?
> It's a dependent patch.
That's the one that cause most of the warnings...
--
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-05-06 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 5:25 [PATCH 0/2] wireless: Make and use const struct ieee80211_channel Joe Perches
2011-04-29 5:25 ` [PATCH 1/2] wireless: Make struct ieee80211_channel const where possible Joe Perches
2011-04-29 7:11 ` Johannes Berg
2011-04-29 5:25 ` [PATCH 2/2] wireless: Use const struct ieee80211_channel " Joe Perches
2011-04-29 5:25 ` Joe Perches
2011-05-05 18:49 ` [PATCH 0/2] wireless: Make and use const struct ieee80211_channel John W. Linville
2011-05-05 22:21 ` Joe Perches
2011-05-06 13:19 ` John W. Linville [this message]
2011-05-06 16:10 ` Joe Perches
2011-05-11 16:57 ` John W. Linville
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=20110506131922.GA2252@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=joe@perches.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=orinoco-users@lists.sourceforge.net \
/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.