From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: bruno randolf <br1@einfach.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix IBSS code
Date: Thu, 21 Feb 2008 14:43:07 -0500 [thread overview]
Message-ID: <20080221194307.GL3094@tuxdriver.com> (raw)
In-Reply-To: <1203621836.26341.4.camel@johannes.berg>
On Thu, Feb 21, 2008 at 08:23:56PM +0100, Johannes Berg wrote:
>
> On Thu, 2008-02-21 at 12:07 -0500, John W. Linville wrote:
> > On Thu, Feb 21, 2008 at 11:08:33AM +0100, Johannes Berg wrote:
> > > This patch fixes two errors introduced by
> > >
> > > commit 19d35612f3cd7f60dd9174c0100584e21f5a1025
> > > Author: Bruno Randolf <bruno@thinktube.com>
> > > Date: Mon Feb 18 11:21:36 2008 +0900
> > >
> > > mac80211: enable IBSS merging
> > >
> > > The first error is an endianness problem that sparse found and
> > > the second is a build failure when CONFIG_MAC80211_IBSS_DEBUG
> > > is not set.
> >
> > I think I like Pavel's fix for the CONFIG_MAC80211_IBSS_DEBUG build
> > issue better. Do you want to repsin the sparse warning bit? If you
> > like, I can respin it for you -- just let me know.
>
> Eh, where do we stand now? Bruno wanted the message to not be rate
> limited in the DEBUG case, and the endianness fix is definitely
> required.
I'll rebase your original patch on top of what is there now. I.E. the
result will be as if I had only applied your patch.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-02-21 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 10:08 [PATCH] mac80211: fix IBSS code Johannes Berg
2008-02-21 17:07 ` John W. Linville
2008-02-21 19:23 ` Johannes Berg
2008-02-21 19:43 ` John W. Linville [this message]
2008-02-22 0:51 ` bruno randolf
2008-02-21 17:16 ` Pavel Roskin
2008-02-21 17:32 ` John W. Linville
2008-02-21 18:27 ` Pavel Roskin
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=20080221194307.GL3094@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--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 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.