From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Alex Davis <alex14641@yahoo.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Kernel bug in bcm43xx-d80211
Date: Mon, 19 Feb 2007 17:30:47 -0500 [thread overview]
Message-ID: <1171924247.2257.31.camel@dv> (raw)
In-Reply-To: <1171923128.15489.35.camel@johannes.berg>
On Mon, 2007-02-19 at 23:12 +0100, Johannes Berg wrote:
> On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> >
> > Feb 19 16:17:42 boss kernel: [ 377.359573] BUG: unable to handle kernel NULL pointer dereference
> > at virtual address 00000002
>
> Probably caused by my recent changes that accidentally broke d80211
> pretty much completely. Patches are on the linux-wireless mailing list.
Johannes, would it be possible to commit patches faster, please? Now
that I told Michael about git-update-server-info, his changes are
downloadable as soon as he makes a commit. wireless-dev.git, on the
other hand, is a mess and has been for some time (since Friday, I
believe).
It is a problem for projects like DadWifi that recommend to use the top
of wireless-dev.git. Yes, I know, breakage is unavoidable to a certain
degree, but it shouldn't come to the situation when the patches are
known, nobody objects, yet the repository stays broken and all newcomers
have to be told about the problem.
That's not to offend you or anyone. It's just something that would help
a lot.
--
Regards,
Pavel Roskin
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: Alex Davis <alex14641-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Kernel bug in bcm43xx-d80211
Date: Mon, 19 Feb 2007 17:30:47 -0500 [thread overview]
Message-ID: <1171924247.2257.31.camel@dv> (raw)
In-Reply-To: <1171923128.15489.35.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
On Mon, 2007-02-19 at 23:12 +0100, Johannes Berg wrote:
> On Mon, 2007-02-19 at 13:48 -0800, Alex Davis wrote:
> > I go the following Oops with the latest wireless-dev git when starting wpa_supplicant:
> >
> > Feb 19 16:17:42 boss kernel: [ 377.359573] BUG: unable to handle kernel NULL pointer dereference
> > at virtual address 00000002
>
> Probably caused by my recent changes that accidentally broke d80211
> pretty much completely. Patches are on the linux-wireless mailing list.
Johannes, would it be possible to commit patches faster, please? Now
that I told Michael about git-update-server-info, his changes are
downloadable as soon as he makes a commit. wireless-dev.git, on the
other hand, is a mess and has been for some time (since Friday, I
believe).
It is a problem for projects like DadWifi that recommend to use the top
of wireless-dev.git. Yes, I know, breakage is unavoidable to a certain
degree, but it shouldn't come to the situation when the patches are
known, nobody objects, yet the repository stays broken and all newcomers
have to be told about the problem.
That's not to offend you or anyone. It's just something that would help
a lot.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-19 22:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:48 Kernel bug in bcm43xx-d80211 Alex Davis
2007-02-19 22:12 ` Johannes Berg
2007-02-19 22:30 ` Pavel Roskin [this message]
2007-02-19 22:30 ` Pavel Roskin
2007-02-19 22:36 ` Johannes Berg
2007-02-19 22:21 ` Pavel Roskin
2007-02-19 23:48 ` Alex Davis
2007-02-20 0:08 ` Johannes Berg
2007-02-20 0:14 ` Johannes Berg
2007-02-20 0:23 ` Jiri Benc
2007-02-20 0:16 ` Larry Finger
2007-02-20 0:24 ` Pavel Roskin
2007-02-20 0:40 ` Alex Davis
2007-02-20 0:48 ` Pavel Roskin
2007-02-20 0:51 ` Jiri Benc
2007-02-20 3:04 ` Alex Davis
2007-02-20 3:54 ` Pavel Roskin
2007-02-20 8:25 ` Johannes Berg
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=1171924247.2257.31.camel@dv \
--to=proski@gnu.org \
--cc=alex14641@yahoo.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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.