All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: linux-usb@vger.kernel.org
Cc: Wolfram Sang <wsa-dev@sang-engineering.com>,
	devel@driverdev.osuosl.org, linux-media@vger.kernel.org
Subject: [PATCH 0/6] staging: don't print error when allocating urb fails
Date: Thu, 11 Aug 2016 23:23:37 +0200	[thread overview]
Message-ID: <1470950624-26455-1-git-send-email-wsa-dev@sang-engineering.com> (raw)

This per-subsystem series is part of a tree wide cleanup. usb_alloc_urb() uses
kmalloc which already prints enough information on failure. So, let's simply
remove those "allocation failed" messages from drivers like we did already for
other -ENOMEM cases. gkh acked this approach when we talked about it at LCJ in
Tokyo a few weeks ago.


Wolfram Sang (6):
  staging: comedi: drivers: usbduxfast: don't print error when
    allocating urb fails
  staging: media: lirc: lirc_imon: don't print error when allocating urb
    fails
  staging: media: lirc: lirc_sasem: don't print error when allocating
    urb fails
  staging: most: hdm-usb: hdm_usb: don't print error when allocating urb
    fails
  staging: rtl8192u: r8192U_core: don't print error when allocating urb
    fails
  staging: vt6656: main_usb: don't print error when allocating urb fails

 drivers/staging/comedi/drivers/usbduxfast.c |  4 +---
 drivers/staging/media/lirc/lirc_imon.c      |  9 ++-------
 drivers/staging/media/lirc/lirc_sasem.c     |  5 -----
 drivers/staging/most/hdm-usb/hdm_usb.c      |  4 +---
 drivers/staging/rtl8192u/r8192U_core.c      |  5 +----
 drivers/staging/vt6656/main_usb.c           | 12 +++---------
 6 files changed, 8 insertions(+), 31 deletions(-)

-- 
2.8.1


             reply	other threads:[~2016-08-11 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 21:23 Wolfram Sang [this message]
2016-08-11 21:23 ` [PATCH 2/6] staging: media: lirc: lirc_imon: don't print error when allocating urb fails Wolfram Sang
2016-08-11 21:23 ` [PATCH 3/6] staging: media: lirc: lirc_sasem: " Wolfram Sang

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=1470950624-26455-1-git-send-email-wsa-dev@sang-engineering.com \
    --to=wsa-dev@sang-engineering.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 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.