From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Angelo Dell'Aera" <buffer@antifork.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-Net <linux-net@vger.kernel.org>
Subject: Re: airo_cs problem - kernel 2.6.1
Date: Tue, 27 Jan 2004 12:45:38 +0000 [thread overview]
Message-ID: <20040127124538.E18409@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040127130709.50a3eaae.buffer@antifork.org>; from buffer@antifork.org on Tue, Jan 27, 2004 at 01:07:09PM +0100
On Tue, Jan 27, 2004 at 01:07:09PM +0100, Angelo Dell'Aera wrote:
> Today I experienced this problem with a Cisco Aironet 350.
> I just want to point out it's the first time it happens.
> In fact, I still used this NIC on this kernel (2.6.1) without
> any kind of problem. Attached is an extract from my log.
AAARRRGGGHHH.
Whatever, it's a known problem with a history of at about three months.
The last message seems to be the maintainer saying that he has a patch
ready and will send to Jeff. I've no idea if that actually happened or
not.
I'm going to suggest that it gets marked as a broken and unmaintained
driver, or I'm going to bypass the maintainers and submit an _untested_
fix directly to Andrew/Linus. I don't want to do either, but...
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-01-27 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 12:07 airo_cs problem - kernel 2.6.1 Angelo Dell'Aera
2004-01-27 12:45 ` Russell King [this message]
2004-01-27 12:55 ` Russell King
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=20040127124538.E18409@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=buffer@antifork.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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.