netdev - Re: [PATCH 5/5] net-next:asix: v2 update VERSION only

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:	Wed, 16 Nov 2011 22:18:57 -0500
From:	Valdis.Kletnieks@...edu
To:	Grant Grundler <grundler@...omium.org>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, Allan Chou <allan@...x.com.tw>,
	Freddy Xin <freddy@...x.com.tw>
Subject: Re: [PATCH 5/5] net-next:asix: v2 update VERSION only

On Tue, 15 Nov 2011 17:37:47 PST, Grant Grundler said:

> Upstream drivers are routinely back ported to distro releases. Version
> is the primary means for a vendor (like ASIX) to determine what was
> back ported. Distro maintainers and 1st tier support organizations
> also need to track versions and "ethtool -i" is the canonical way to
> look this up on a running system.

Oh, OK.  I figured the distro would know what they backported based on the
kernel version they generated - I forgot that sometimes users will bypass the
distro and go to the upstream vendor, and you may not know what their distro
had done...


Content of type "application/pgp-signature" skipped