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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 3 Feb 2009 01:26:14 +0100
From:	"Filip Aben" <F.Aben@...ion.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	<gregkh@...e.de>, <netdev@...r.kernel.org>,
	<linux-usb@...r.kernel.org>
Subject: RE: [PATCH] hso: add new device id's



> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: maandag 2 februari 2009 23:03
> To: Filip Aben
> Cc: gregkh@...e.de; netdev@...r.kernel.org; linux-usb@...r.kernel.org
> Subject: Re: [PATCH] hso: add new device id's
> 
> From: Filip Aben <f.aben@...ion.com>
> Date: Mon, 02 Feb 2009 15:59:05 +0100
> 
> > This patch adds a few device id's and removes one which will never
be
> used.
> >
> > Signed-off-by: Filip Aben <f.aben@...ion.com>
> 
> Why won't 0xaf0/0xd051 ever be used?
> 
> You should explain such things in your commit message,
> that way I don't have to ask.

That ID was used in an internal engineering version of a device and 
will never see commercial light.
Even if this ID will be 'recycled' in the future, which is very
unlikely, 
I don't know what kind of device will be behind it. Therefore it's safer
to remove it.

Regards,

Filip-
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ