linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: greg@kroah.com, kamal.mostafa@canonical.com,
	luis.henriques@canonical.com, jslaby@suse.cz
Cc: clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [v3.10.y][v3.11.y][3.12.y][v3.13.y][v3.14.y][SRU][PATCH 0/1][V2] ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined
Date: Wed, 18 Jun 2014 14:32:15 -0400	[thread overview]
Message-ID: <cover.1403113867.git.joseph.salisbury@canonical.com> (raw)

Hello,

Please consider including upstream commit b7a77235 in the next v3.13.y release.  It was included upstream as of v3.15-rc5.  It has been tested and confirmed to resolve http://bugs.launchpad.net/bugs/1319457 .

commit b7a7723513dc89f83d6df13206df55d4dc26e825
Author: Sander Eikelenboom <linux@eikelenboom.it>
Date:   Fri May 2 15:09:27 2014 +0200

    ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined


This original commit does not apply cleanly to v3.13, so I performed a backport, which is in email 1/1.  The backport has been tested and cleanly applies to upstream 3.10.y, 3.11.y, 3.12.y and 3.14.y.  The backport is not applicable to longterm stable 3.2.y or 3.4.y.


Sander Eikelenboom (1):
  ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log
    while DEBUG not defined

 sound/usb/pcm.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
2.0.0


             reply	other threads:[~2014-06-18 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 18:32 Joseph Salisbury [this message]
2014-06-18 18:32 ` [v3.10.y][v3.11.y][v3.12.y][v3.13.y][v3.14.y][PATCH 1/1][V2] ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined Joseph Salisbury
2014-06-19  1:52   ` Ben Hutchings
2014-06-20 15:21     ` Joseph Salisbury
2014-06-20 18:21       ` Joseph Salisbury
2014-06-21 12:05         ` Ben Hutchings
2014-06-21 19:48           ` Greg KH
2014-07-07 22:26             ` Greg KH

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=cover.1403113867.git.joseph.salisbury@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=clm@fb.com \
    --cc=greg@kroah.com \
    --cc=jbacik@fb.com \
    --cc=jslaby@suse.cz \
    --cc=kamal.mostafa@canonical.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).