mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Greg KH <greg@kroah.com>
Cc: Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	usb-storage@lists.one-eyed-alien.net,
	Linux USB Mailing List <linux-usb@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Felipe Balbi <balbi@ti.com>
Subject: [PATCH 00/13] Sparse fixes
Date: Tue, 15 Nov 2011 09:53:27 +0200	[thread overview]
Message-ID: <1321343620-10794-1-git-send-email-balbi@ti.com> (raw)

Hi Greg,

Here are a few sparse fixups for the storage drivers.
Compile tested with allyesconfig and allmodconfig.

Felipe Balbi (13):
  usb: storage: alauda: fix sparse warnings
  usb: storage: cypress: fix sparse warning
  usb: storage: datafab: fix sparse warning
  usb: storage: ene_ub6250: fix sparse warnings
  usb: storage: freecom: fix sparse warning
  usb: storage: isd200: fix sparse warning
  usb: storage: jumpshot: fix sparse warning
  usb: storage: karma: fix sparse warning
  usb: storage: onetouch: fix sparse warning
  usb: storagE: realtek_cr: fix sparse warnings
  usb: storage: sddr09: fix sparse warning
  usb: storage: sddr55: fix sparse warning
  usb: storage: shuttle_usbat: fix sparse warning

 drivers/usb/storage/alauda.c        |    2 +-
 drivers/usb/storage/cypress_atacb.c |    2 +-
 drivers/usb/storage/datafab.c       |    2 +-
 drivers/usb/storage/ene_ub6250.c    |   12 ++++++------
 drivers/usb/storage/freecom.c       |    2 +-
 drivers/usb/storage/isd200.c        |    2 +-
 drivers/usb/storage/jumpshot.c      |    2 +-
 drivers/usb/storage/karma.c         |    2 +-
 drivers/usb/storage/onetouch.c      |    2 +-
 drivers/usb/storage/realtek_cr.c    |   11 +++++------
 drivers/usb/storage/sddr09.c        |    2 +-
 drivers/usb/storage/sddr55.c        |    2 +-
 drivers/usb/storage/shuttle_usbat.c |    2 +-
 13 files changed, 22 insertions(+), 23 deletions(-)

-- 
1.7.8.rc0


             reply	other threads:[~2011-11-15  7:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  7:53 Felipe Balbi [this message]
2011-11-15  7:53 ` [PATCH 01/13] usb: storage: alauda: fix sparse warnings Felipe Balbi
2011-11-15  7:53 ` [PATCH 02/13] usb: storage: cypress: fix sparse warning Felipe Balbi
2011-11-15  7:53 ` [PATCH 03/13] usb: storage: datafab: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 04/13] usb: storage: ene_ub6250: fix sparse warnings Felipe Balbi
2011-11-15  7:53 ` [PATCH 05/13] usb: storage: freecom: fix sparse warning Felipe Balbi
2011-11-15  7:53 ` [PATCH 06/13] usb: storage: isd200: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 07/13] usb: storage: jumpshot: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 08/13] usb: storage: karma: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 09/13] usb: storage: onetouch: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 10/13] usb: storagE: realtek_cr: fix sparse warnings Felipe Balbi
2011-11-15  7:53 ` [PATCH 11/13] usb: storage: sddr09: fix sparse warning Felipe Balbi
2011-11-15  7:53 ` [PATCH 12/13] usb: storage: sddr55: " Felipe Balbi
2011-11-15  7:53 ` [PATCH 13/13] usb: storage: shuttle_usbat: " Felipe Balbi

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=1321343620-10794-1-git-send-email-balbi@ti.com \
    --to=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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®