From: "Jesse Huang" <jesse@icplus.com.tw>
To: "Andrew Morton" <akpm@osdl.org>, "Roland Dreier" <rdreier@cisco.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<jgarzik@pobox.com>
Subject: Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh
Date: Mon, 2 Oct 2006 15:10:55 +0800 [thread overview]
Message-ID: <018401c6e5f1$e76590f0$4964a8c0@icplus.com.tw> (raw)
In-Reply-To: ada3ba7xkvx.fsf@cisco.com
Sorry, I had typed wrong word.
It is because patent issue.
Thnaks.
----- Original Message -----
From: "Roland Dreier" <rdreier@cisco.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: "Jesse Huang" <jesse@icplus.com.tw>; <linux-kernel@vger.kernel.org>;
<netdev@vger.kernel.org>; <jgarzik@pobox.com>
Sent: Monday, October 02, 2006 3:00 PM
Subject: Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh
> > For pattern issue need to remove TxStartThresh and RxEarlyThresh.
> Please describe this issue more completely.
>
> What are the implications of simply removing this feature? Presumably
that
> code was there for a reason..
Actually I think this patch needs to be handled delicately -- because
based on earlier emails from Jesse
(http://www.mail-archive.com/netdev@vger.kernel.org/msg22254.html),
I am pretty sure that "pattern" is a typo for "patent". So I guess
the question is what exactly the patent covers and what the
implications of having the current kernel code are.
- R.
next prev parent reply other threads:[~2006-10-02 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 18:23 [PATCH 1/5] remove TxStartThresh and RxEarlyThresh Jesse Huang
2006-10-02 6:53 ` Andrew Morton
2006-10-02 7:00 ` Roland Dreier
2006-10-02 7:10 ` Jesse Huang [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-14 19:55 Jesse Huang
2006-10-15 21:26 ` Benjamin Herrenschmidt
2006-10-15 22:59 ` Alan Cox
2006-10-16 1:39 ` Valdis.Kletnieks
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='018401c6e5f1$e76590f0$4964a8c0@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 \
--cc=rdreier@cisco.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 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.