From: Johan Hovold <johan@kernel.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Johan Hovold <johan@kernel.org>,
Marek Belisko <marek@goldelico.com>,
gregkh@linuxfoundation.org, corbet@lwn.net,
linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, gta04-owner@goldelico.com,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH v2] Documentation usb serial: fixed how to provide vendor and product id
Date: Tue, 21 Apr 2015 15:03:10 +0200 [thread overview]
Message-ID: <20150421130310.GA31609@localhost> (raw)
In-Reply-To: <87oamhofse.fsf@nemi.mork.no>
On Tue, Apr 21, 2015 at 01:57:05PM +0200, Bjørn Mork wrote:
> Johan Hovold <johan@kernel.org> writes:
> > On Mon, Apr 20, 2015 at 10:15:20PM +0200, Marek Belisko wrote:
> >> From: "H. Nikolaus Schaller" <hns@goldelico.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
next prev parent reply other threads:[~2015-04-21 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 20:09 [PATCH v2] Documentation usb serial: fixed how to provide vendor and product id Marek Belisko
2015-04-14 7:30 ` Johan Hovold
2015-04-20 20:15 ` Marek Belisko
2015-04-21 7:47 ` Johan Hovold
2015-04-21 11:57 ` Bjørn Mork
2015-04-21 13:03 ` Johan Hovold [this message]
2015-05-07 15:45 ` Jonathan Corbet
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=20150421130310.GA31609@localhost \
--to=johan@kernel.org \
--cc=bjorn@mork.no \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek@goldelico.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox