From: "Jesse Huang" <jesse@icplus.com.tw>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<jgarzik@pobox.com>
Subject: Re: What is current sundance.c status
Date: Fri, 13 Oct 2006 09:14:30 +0800 [thread overview]
Message-ID: <00ac01c6ee64$ef637210$2d32fea9@icplus.com.tw> (raw)
In-Reply-To: 20061011195540.06b2ef13.akpm@osdl.org
Ok, I will generate those again with descriptions.
Thank you!
Best Regards,
Jesse Huang.
----- Original Message -----
From: "Andrew Morton" <akpm@osdl.org>
To: "Jesse Huang" <jesse@icplus.com.tw>
Cc: <linux-kernel@vger.kernel.org>; <netdev@vger.kernel.org>;
<jgarzik@pobox.com>
Sent: Thursday, October 12, 2006 10:55 AM
Subject: Re: What is current sundance.c status
On Thu, 12 Oct 2006 10:29:37 +0800
"Jesse Huang" <jesse@icplus.com.tw> wrote:
> Would you tell me what is the current IP100A status? Should I
re-generate patches again. Would it put into kernel or not?
I'm sitting on a copy of them. I didn't send them to Jeff last time
because:
sundance-remove-txstartthresh-and-rxearlythresh.patch
There's no description of what this patent issue is.
sundance-fix-tx-pause-bug-reset_tx-intr_handler.patch
There's no description of the bug which got fixed, nor how this patch
fixes it.
sundance-change-phy-address-search-from-phy=1-to-phy=0.patch
There's a (small) possibility that this will break on hardware which
_doesn't_ have a phy at address 0.
sundance-correct-initial-and-close-hardware-step.patch
There's no real description of the bug which is being fixed, nor of how
this patch fixes it.
sundance-solve-host-error-problem-in-low-performance-embedded.patch
No description of what the "host error problem" is, nor of what causes
it, nor of how this patch fixes it.
So generally these patches are a bit worrying, and it is hard to gauge what
their risk factor is.
prev parent reply other threads:[~2006-10-13 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <004301c6eda6$437ac070$2d32fea9@icplus.com.tw>
2006-10-12 2:55 ` What is current sundance.c status Andrew Morton
2006-10-13 1:14 ` Jesse Huang [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='00ac01c6ee64$ef637210$2d32fea9@icplus.com.tw' \
--to=jesse@icplus.com.tw \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox