All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Max Schulze <max.schulze@posteo.de>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: USB: serial: simple: add Motorola Tetra driver for TPG2200
Date: Mon, 7 Jan 2019 16:42:29 +0100	[thread overview]
Message-ID: <20190107154229.GE14782@localhost> (raw)

On Mon, Jan 07, 2019 at 08:31:49AM +0100, Max Schulze wrote:
> Add new Motorola Tetra (simple) driver for Motorola Solutions TETRA PEI
> device

I rephrased the summary and comment above since you're adding a new
device id to an existing driver (rather than a new driver).

> T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=480 MxCh= 0
> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=0cad ProdID=9016 Rev=24.16
> S:  Manufacturer=Motorola Solutions, Inc.
> S:  Product=TETRA PEI interface
> C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple
> I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple
> 
> Signed-off-by: Max Schulze <max.schulze@posteo.de>
> Tested-by: Max Schulze <max.schulze@posteo.de>

And no need to add Tested-by for your own patches; submissions are
always supposed to be tested.

Applied for -rc2.

Thanks,
Johan

WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Max Schulze <max.schulze@posteo.de>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: simple: add Motorola Tetra driver for TPG2200
Date: Mon, 7 Jan 2019 16:42:29 +0100	[thread overview]
Message-ID: <20190107154229.GE14782@localhost> (raw)
In-Reply-To: <20190107073149.8214-1-max.schulze@posteo.de>

On Mon, Jan 07, 2019 at 08:31:49AM +0100, Max Schulze wrote:
> Add new Motorola Tetra (simple) driver for Motorola Solutions TETRA PEI
> device

I rephrased the summary and comment above since you're adding a new
device id to an existing driver (rather than a new driver).

> T:  Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  4 Spd=480 MxCh= 0
> D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
> P:  Vendor=0cad ProdID=9016 Rev=24.16
> S:  Manufacturer=Motorola Solutions, Inc.
> S:  Product=TETRA PEI interface
> C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple
> I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=usb_serial_simple
> 
> Signed-off-by: Max Schulze <max.schulze@posteo.de>
> Tested-by: Max Schulze <max.schulze@posteo.de>

And no need to add Tested-by for your own patches; submissions are
always supposed to be tested.

Applied for -rc2.

Thanks,
Johan

             reply	other threads:[~2019-01-07 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 15:42 Johan Hovold [this message]
2019-01-07 15:42 ` [PATCH] USB: serial: simple: add Motorola Tetra driver for TPG2200 Johan Hovold
  -- strict thread matches above, loose matches on Subject: below --
2019-01-07  7:31 Max Schulze
2019-01-07  7:31 ` [PATCH] " Max Schulze

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=20190107154229.GE14782@localhost \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=max.schulze@posteo.de \
    /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.