public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Johan Hovold <jhovold@gmail.com>
Subject: [GIT PATCH] USB fixes for 3.12-final
Date: Fri, 1 Nov 2013 09:59:31 -0700	[thread overview]
Message-ID: <20131101165931.GA18020@kroah.com> (raw)

The following changes since commit 959f58544b7f20c92d5eb43d1232c96c15c01bfb:

  Linux 3.12-rc7 (2013-10-27 16:12:03 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-3.12-rc8

for you to fetch changes up to e1466ad5b1aeda303f9282463d55798d2eda218c:

  USB: serial: ftdi_sio: add id for Z3X Box device (2013-11-01 09:33:56 -0700)

----------------------------------------------------------------
USB fixes for 3.12-final

Here is a set of patches that revert all of the changes done to the
pl2303 USB serial driver in the 3.12-rc timeframe, as it turns out they
break some devices that work just fine on 3.11.  As it's not a good idea
to break working systems, drop them all and they will be reworked for
future kernel versions such that there is no breakage.

I've also included a MAINTAINERS update for the USB serial subsystem and
a new device id for the ftdi_sio driver as well.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Greg KH (1):
      USB: Maintainers change for usb serial drivers

Greg Kroah-Hartman (12):
      Revert "USB: pl2303: distinguish between original and cloned HX chips"
      Revert "pl2303: improve the chip type detection/distinction"
      Revert "pl2303: improve the chip type information output on startup"
      Revert "pl2303: simplify the else-if contruct for type_1 chips in pl2303_startup()"
      Revert "usb: pl2303: add two comments concerning the supported baud rates with HX chips"
      Revert "usb: pl2303: also use the divisor based baud rate encoding method for baud rates < 115200 with HX chips"
      Revert "usb: pl2303: increase the allowed baud rate range for the divisor based encoding method"
      Revert "usb: pl2303: move the two baud rate encoding methods to separate functions"
      Revert "usb: pl2303: remove 500000 baud from the list of standard baud rates"
      Revert "usb: pl2303: do not round to the next nearest standard baud rate for the divisor based baud rate encoding method"
      Revert "usb: pl2303: fix+improve the divsor based baud rate encoding method"
      Revert "USB: pl2303: restrict the divisor based baud rate encoding method to the "HX" chip type"

Алексей Крамаренко (1):
      USB: serial: ftdi_sio: add id for Z3X Box device

 MAINTAINERS                       |  53 +-------
 drivers/usb/serial/ftdi_sio.c     |   1 +
 drivers/usb/serial/ftdi_sio_ids.h |   6 +
 drivers/usb/serial/pl2303.c       | 274 ++++++++------------------------------
 4 files changed, 66 insertions(+), 268 deletions(-)

                 reply	other threads:[~2013-11-01 16:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131101165931.GA18020@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jhovold@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox