mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julius Werner <jwerner@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dongjin Kim <tobetter@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Wei Yongjun <yongjun_wei@trendmicro.com.cn>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Simon Glass <sjg@chromium.org>,
	Doug Anderson <dianders@chromium.org>,
	Olof Johansson <olofj@chromium.org>,
	Vivek Gautam <gautam.vivek@samsung.com>,
	Julius Werner <jwerner@chromium.org>
Subject: [PATCH 0/3] usb: misc: usb3503: Fix up usb3503 driver
Date: Fri, 31 May 2013 18:34:49 -0700	[thread overview]
Message-ID: <1370050492-6046-1-git-send-email-jwerner@chromium.org> (raw)

This patch set contains a few minor changes to the recently added SMSC
USB3503 driver. It addresses issues that seem to be either left-over
stopgaps from an early development stage or board-specific hacks,
changing them to defaults that should be most sane and useable for all
platforms that contain this chip.

Julius Werner (3):
  usb: misc: usb3503: Fix up whitespace
  usb: misc: usb3503: Remove hardcoded disabling of ports 2 and 3
  usb: misc: usb3503: Remove 100ms sleep on reset, conform to data
    sheet

 drivers/usb/misc/usb3503.c | 16 +++-------------
 1 file changed, 3 insertions(+), 13 deletions(-)

-- 
1.7.12.4


             reply	other threads:[~2013-06-01  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  1:34 Julius Werner [this message]
2013-06-01  1:34 ` [PATCH 1/3] usb: misc: usb3503: Fix up whitespace Julius Werner
2013-06-01  3:08   ` Dongjin Kim
2013-06-01  1:34 ` [PATCH 2/3] usb: misc: usb3503: Remove hardcoded disabling of ports 2 and 3 Julius Werner
2013-06-01  3:01   ` Dongjin Kim
2013-06-01  1:34 ` [PATCH 3/3] usb: misc: usb3503: Remove 100ms sleep on reset, conform to data sheet Julius Werner
2013-06-01  3:08   ` Dongjin Kim
2013-06-01  2:55 ` [PATCH 0/3] usb: misc: usb3503: Fix up usb3503 driver Olof Johansson

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=1370050492-6046-1-git-send-email-jwerner@chromium.org \
    --to=jwerner@chromium.org \
    --cc=dianders@chromium.org \
    --cc=fengguang.wu@intel.com \
    --cc=gautam.vivek@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=olofj@chromium.org \
    --cc=sjg@chromium.org \
    --cc=tobetter@gmail.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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

all inboxes | Powered by JetHome®