From: Jan Dittmer <j.dittmer@portrix.net>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: kuba@mareimbrium.org, greg@kroah.com, bryder@sgi.com,
linux-kernel@vger.kernel.org, edwin@harddisk-recovery.nl
Subject: Re: FTDI SIO patch to allow custom vendor/product IDs.
Date: Thu, 02 Dec 2004 14:57:32 +0100 [thread overview]
Message-ID: <41AF1F4C.2030707@portrix.net> (raw)
In-Reply-To: <20041202124831.GA31745@bitwizard.nl>
Rogier Wolff wrote:
> +MODULE_PARM(vendor, "i");
> +MODULE_PARM_DESC(vendor, "User specified USB idVendor");
> +
> +MODULE_PARM(product, "i");
> +MODULE_PARM_DESC(product, "User specified USB idProduct");
Use module_param instead.
Jan
next prev parent reply other threads:[~2004-12-02 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 12:48 FTDI SIO patch to allow custom vendor/product IDs Rogier Wolff
2004-12-02 13:34 ` Christoph Hellwig
2004-12-02 18:00 ` Greg KH
2004-12-02 13:57 ` Jan Dittmer [this message]
2004-12-02 14:02 ` Jan Dittmer
2004-12-02 18:00 ` Greg KH
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=41AF1F4C.2030707@portrix.net \
--to=j.dittmer@portrix.net \
--cc=R.E.Wolff@BitWizard.nl \
--cc=bryder@sgi.com \
--cc=edwin@harddisk-recovery.nl \
--cc=greg@kroah.com \
--cc=kuba@mareimbrium.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.