From: Michael Buesch <mb@bu3sch.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linville@tuxdriver.com, st3@riseup.net,
bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH] bcm43xx: Fix array overrun in bcm43xx_geo_init
Date: Thu, 11 May 2006 10:29:11 +0200 [thread overview]
Message-ID: <200605111029.12540.mb@bu3sch.de> (raw)
In-Reply-To: <20060510204200.43ed67fb.akpm@osdl.org>
On Thursday 11 May 2006 05:42, you wrote:
> Michael Buesch <mb@bu3sch.de> wrote:
> >
> > The problem here is that the bcm34xx driver and the ieee80211
> > stack do not agree on what channels are possible for 802.11a.
> > The ieee80211 stack only wants channels between 34 and 165, while
> > the bcm43xx driver accepts anything from 0 to 200. I made the
> > bcm43xx driver comply with the ieee80211 stack expectations, by
> > using the proper constants.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> >
> > [mb]: Reduce stack usage by kzalloc-ing ieee80211_geo
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> I find this changelog confusing. We seem to have two patches, one written
> by Jean and one by yourself, perhaps? And the fact that the changlog
> didn't start with
I simply added one or two lines of code.
> From: Jean Delvare <jdelvare@suse.de>
>
> indicates that you are to be considered the primary author?
No, I forgot about that line.
> btw, we seem to have a number of bcm43xx patches banking up. I don't know
> if John has merged them because we're back in the situation where some of
> John's tree has been merged into Jeff's tree but hasn't gone upstream - so
> my git-wireless.patch generates a massive reject storm against git-netdev.patch
>
> So I suspect that all these bcm43xx might not be making it into 2.6.17.
I think most of the patches should already be merged by john. But I did not
recheck this. It would be bad, if they won't make it for 2.6.17, though,
as they are all heavy bugfixes that prevent hard oopses for people
with special cards, that the developers did not have.
--
Greetings Michael.
prev parent reply other threads:[~2006-05-11 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 15:23 [PATCH] bcm43xx: Fix array overrun in bcm43xx_geo_init Michael Buesch
2006-05-11 3:42 ` Andrew Morton
2006-05-11 8:29 ` Michael Buesch [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=200605111029.12540.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@osdl.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=st3@riseup.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 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).