From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff
Date: Thu, 19 Mar 2009 22:46:51 +0100 [thread overview]
Message-ID: <1237499211.5100.123.camel@johannes.local> (raw)
In-Reply-To: <20090319204406.GA14753@tesla>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Thu, 2009-03-19 at 13:44 -0700, Luis R. Rodriguez wrote:
> On Thu, Mar 19, 2009 at 02:40:52PM -0700, Johannes Berg wrote:
> > On Thu, 2009-03-19 at 13:28 -0700, Luis R. Rodriguez wrote:
> > > On Thu, Mar 19, 2009 at 12:40 PM, Johannes Berg
> > > <johannes@sipsolutions.net> wrote:
> > > > John,
> > > >
> > > > please back out this series, I'm not sure I agree with the concept and
> > > > I'm sure there are potential bugs that can make it segfault.
> > >
> > > Can you be more elaborate?
> >
> > reg_process_ht_flags_channel doesn't initialise channel_before and
> > channel_after.
>
> I can fix that, two lines.
I know, but I wouldn't want having bug reports from this code until John
gets to merging again :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-19 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 5:54 [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 1/6] cfg80211: Process regulatory max bandwidth checks for HT40 Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 2/6] wireless: rename IEEE80211_CHAN_NO_FAT_* to HT40-/+ Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 3/6] mac80211: check if HT40+/- is allowed before sending assoc Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 4/6] cfg80211: check allowed channel type upon userspace requests Luis R. Rodriguez
2009-03-20 10:45 ` Johannes Berg
2009-03-19 5:54 ` [PATCH v2 5/6] cfg80211: send channel max bandwidth to userspace Luis R. Rodriguez
2009-03-19 5:54 ` [PATCH v2 6/6] cfg80211: send to userspace if HT40-/+ is allowed on each channel Luis R. Rodriguez
2009-03-19 19:40 ` [PATCH v2 0/6] Use the regulatory bandwidth and export HT40 stuff Johannes Berg
2009-03-19 20:28 ` Luis R. Rodriguez
2009-03-19 21:40 ` Johannes Berg
2009-03-19 20:44 ` Luis R. Rodriguez
2009-03-19 21:46 ` Johannes Berg [this message]
2009-03-19 20:56 ` Luis R. Rodriguez
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=1237499211.5100.123.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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 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).