linux-kernel - Re: [PATCH v2] Documentation usb serial: fixed how to provide vendor and product id

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, 21 Apr 2015 15:03:10 +0200
From:	Johan Hovold <johan@...nel.org>
To:	Bjørn Mork <bjorn@...k.no>
Cc:	Johan Hovold <johan@...nel.org>,
	Marek Belisko <marek@...delico.com>,
	gregkh@...uxfoundation.org, corbet@....net,
	linux-usb@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, gta04-owner@...delico.com,
	"H. Nikolaus Schaller" <hns@...delico.com>
Subject: Re: [PATCH v2] Documentation usb serial: fixed how to provide vendor
 and product id

On Tue, Apr 21, 2015 at 01:57:05PM +0200, Bjørn Mork wrote:
> Johan Hovold <johan@...nel.org> writes:
> > On Mon, Apr 20, 2015 at 10:15:20PM +0200, Marek Belisko wrote:
> >> From: "H. Nikolaus Schaller" <hns@...delico.com>
> >> 
> >> The parameters vendor= and product= are only available
> >> if compiled as a kernel module
> 
> Really? I believe you should be able to do
> 
>   usbserial.vendor=vid usbserial.product=pid
> 
> on the command line if usbserial is built-in. Not that I recommend doing
> that.  But it should work.

You're right, the commit message is a little misleading, but the updated
documentation is correct. The current text does not mention the option
to pass module parameters on the kernel command line explicitly either.

Johan
--
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/