From: Michael Buesch <mb@bu3sch.de>
To: Pavel Roskin <proski@gnu.org>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: More breakage in wireless-dev.git
Date: Sat, 17 Feb 2007 18:56:07 +0100 [thread overview]
Message-ID: <200702171856.08068.mb@bu3sch.de> (raw)
In-Reply-To: <20070217125127.hfrlkwkgo884sos8@webmail.spamcop.net>
On Saturday 17 February 2007 18:51, Pavel Roskin wrote:
> > The slab error on the end of your dmesg is interresting, though.
>
> I'll have a closer look.
I think that's fixed now, too.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-17 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 5:41 More breakage in wireless-dev.git Pavel Roskin
2007-02-17 8:06 ` Pavel Roskin
2007-02-17 13:02 ` Michael Buesch
2007-02-17 16:44 ` Pavel Roskin
2007-02-17 16:55 ` Michael Buesch
2007-02-17 17:30 ` Michael Buesch
2007-02-17 17:51 ` Pavel Roskin
2007-02-17 17:56 ` Michael Buesch [this message]
2007-02-17 18:10 ` Pavel Roskin
2007-02-17 18:14 ` Michael Buesch
2007-02-17 18:26 ` Pavel Roskin
2007-02-17 18:30 ` Michael Buesch
2007-02-17 18:58 ` 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=200702171856.08068.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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 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).