From: Jeff Garzik <jeff@garzik.org>
To: Krzysztof Halasa <khc@pm.waw.pl>, Francois Romieu <romieu@fr.zoreil.com>
Cc: Netdev List <netdev@vger.kernel.org>
Subject: [Fwd: Re: wan/pc300 bug found]
Date: Tue, 14 Nov 2006 09:42:07 -0500 [thread overview]
Message-ID: <4559D5BF.3080605@garzik.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
FYI... I'm certainly willing to remove pc300, if nobody wants it.
But I am unsure whether this is a case of "vendor doesn't care" or
"users don't care", which are two very different things...
Jeff
[-- Attachment #2: Re: wan/pc300 bug found --]
[-- Type: message/rfc822, Size: 2050 bytes --]
From: "Squassoni, Daniela" <Daniela.Squassoni@avocent.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "Rosalino, Wanda" <Wanda.Rosalino@avocent.com>
Subject: RE: wan/pc300 bug found
Date: Tue, 14 Nov 2006 05:43:29 -0600
Message-ID: <1EF69AC43C5ABC49985E42B84575ADB7091CEA8E@hsv-email.corp.avocent.com>
Jeff,
As PC300 is not being produced anymore, we decided that the best solution is to remove its driver from the kernel. I will send you a patch to do so, as soon as possible.
Best regards,
Daniela
-----Original Message-----
From: Jeff Garzik [mailto:jeff@garzik.org]
Sent: Sun 10/1/2006 1:35 PM
To: pc300@cyclades.com; khc@pm.waw.pl; netdev@vger.kernel.org; LKML; Andrew Morton
Subject: wan/pc300 bug found
The following gcc warning indicates a bug:
drivers/net/wan/pc300_drv.c: In function 'cpc_open':
drivers/net/wan/pc300_drv.c:2870: warning: 'br' may be used uninitialized in this function
clock_rate_calc() is not checked for a negative return value.
next reply other threads:[~2006-11-14 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 14:42 Jeff Garzik [this message]
2006-11-14 14:56 ` [Fwd: Re: wan/pc300 bug found] Arnaldo Carvalho de Melo
2006-11-14 15:55 ` Krzysztof Halasa
2006-12-16 16:50 ` Jeff Garzik
2007-01-30 15:00 ` Krzysztof Halasa
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=4559D5BF.3080605@garzik.org \
--to=jeff@garzik.org \
--cc=khc@pm.waw.pl \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).