linux-kernel - Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 2 Oct 2006 15:10:55 +0800
From:	"Jesse Huang" <jesse@...lus.com.tw>
To:	"Andrew Morton" <akpm@...l.org>,
	"Roland Dreier" <rdreier@...co.com>
Cc:	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
	<jgarzik@...ox.com>
Subject: Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh

Sorry, I had typed wrong word.

It is because patent issue.

Thnaks.
----- Original Message ----- 
From: "Roland Dreier" <rdreier@...co.com>
To: "Andrew Morton" <akpm@...l.org>
Cc: "Jesse Huang" <jesse@...lus.com.tw>; <linux-kernel@...r.kernel.org>;
<netdev@...r.kernel.org>; <jgarzik@...ox.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.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/