From: Michael Buesch <mb@bu3sch.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: bcm43xx-dev@lists.berlios.de,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Current linus git bcm4xxx broken for me
Date: Fri, 14 Apr 2006 13:43:04 +0200 [thread overview]
Message-ID: <200604141343.05053.mb@bu3sch.de> (raw)
In-Reply-To: <1144972957.5006.2.camel@localhost.localdomain>
On Friday 14 April 2006 02:02, Benjamin Herrenschmidt wrote:
> I get that with current upstream git :
>
> [ 34.127738] bcm43xx: Chip ID 0x4318, rev 0x2
^^^^^^
known broken
We work at it.
--
Greetings Michael.
prev parent reply other threads:[~2006-04-14 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 0:02 Current linus git bcm4xxx broken for me Benjamin Herrenschmidt
2006-04-14 0:35 ` Benjamin Herrenschmidt
2006-04-15 19:27 ` Johannes Berg
2006-04-14 11:43 ` 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=200604141343.05053.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox