From: Greg KH <gregkh@linuxfoundation.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: johan@kernel.org, corbet@lwn.net,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
GTA04 owners <gta04-owner@goldelico.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: [PATCH] Documentation: usb: serial: fixed how to provide vendor and product id
Date: Thu, 26 Mar 2015 12:42:47 +0100 [thread overview]
Message-ID: <20150326114247.GA16916@kroah.com> (raw)
In-Reply-To: <CAAfyv34=bVB1e7O40HuF226cY0bSy_tF3ODn0c1CN=wQ_X++Hg@mail.gmail.com>
On Thu, Mar 26, 2015 at 11:41:24AM +0100, Belisko Marek wrote:
> On Thu, Mar 26, 2015 at 10:53 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Mar 25, 2015 at 09:53:34PM +0100, Marek Belisko wrote:
> >> From: "H. Nikolaus Schaller" <hns@goldelico.com>
> >>
> >> While trying to test the Pyra GSM/GPS/3G module I had reconfigured
> >> the USB interface by mistake and therefore needed to run a different
> >> USB driver than CSC-ACM. It turned out that I need the "usbserial" driver.
> >>
> >> This file is an official description how to use it:
> >> Documentation/usb/usb-serial.txt
> >>
> >> But it is outdated. The parameters vendor= and product= are no longer
> >> available since ca. 3.12 which means that documentation is lagging behind
> >> quite some time.
> >>
> >> Here was the solution:
> >>
> >> https://bbs.archlinux.org/viewtopic.php?id=175499
> >>
> >> insmod usbserial vendor=0x#### product=0x####
> >>
> >> becomes (first #### is vendor, second is product)
> >>
> >> modprobe usbserial
> >> echo #### #### >/sys/bus/usb-serial/drivers/generic/new_id
> >>
> >> This patch changes the documentation file as needed.
> >>
> >> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
> >
> > You are forwarding on a patch from someone else, why didn't you also
> > sign-off on it? Do you not agree with it?
> I wasn't involved in patch development I just review it and forward.
If you reviewed and forwarded it, why did you not add a signed-off-by:
to it? Do you not think it is acceptable for merging? If not, then we
shouldn't either :)
thanks,
greg k-h
next prev parent reply other threads:[~2015-03-26 11:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 20:53 [PATCH] Documentation: usb: serial: fixed how to provide vendor and product id Marek Belisko
2015-03-26 9:53 ` Greg KH
2015-03-26 10:41 ` Belisko Marek
2015-03-26 11:34 ` Dr. H. Nikolaus Schaller
2015-03-26 11:42 ` Greg KH [this message]
2015-03-28 13:37 ` Marek Belisko
2015-03-30 7:45 ` Johan Hovold
2015-03-30 9:32 ` Dr. H. Nikolaus Schaller
2015-03-30 9:40 ` [Gta04-owner] " Dr. H. Nikolaus Schaller
2015-03-30 10:10 ` Johan Hovold
2015-03-30 10:08 ` Johan Hovold
2015-04-02 14:25 ` Dr. H. Nikolaus Schaller
2015-04-02 14:34 ` Johan Hovold
2015-04-02 10:12 ` Jonathan Corbet
2015-04-02 10:35 ` Johan Hovold
2015-04-02 10:39 ` Dr. H. Nikolaus Schaller
2015-04-02 12:14 ` 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=20150326114247.GA16916@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=johan@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek.belisko@gmail.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