From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Greg KH <greg@kroah.com>
Cc: kamal.mostafa@canonical.com, perex@perex.cz, tiwai@suse.de,
eldad@fogrefinery.com, clemens@ladisch.de,
tim.gardner@canonical.com, stern@rowland.harvard.edu,
linux@eikelenboom.it, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [v3.13.y][SRU][PATCH 0/1] ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined
Date: Wed, 18 Jun 2014 13:42:18 -0400 [thread overview]
Message-ID: <53A1CF7A.2050009@canonical.com> (raw)
In-Reply-To: <20140618174328.GB11977@kroah.com>
On 06/18/2014 01:43 PM, Greg KH wrote:
> On Wed, Jun 18, 2014 at 01:14:05PM -0400, Joseph Salisbury wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1319457
>>
>> 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 .
> Please get a good email client and wrap your lines :(
Hmm, not sure why git send-email did that, but I'll fix it.
>
>> 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 commit does not apply cleanly to v3.13, so I performed a backport, which is in email 1/1.
> Any reason this shouldn't also be in 3.14-stable?
Yes it should also be in 3.14 stable. I'll send a v2 of the patch.
>
> thanks,
>
> greg k-h
Thanks for the feedback.
next prev parent reply other threads:[~2014-06-18 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 17:14 [v3.13.y][SRU][PATCH 0/1] ALSA: usb-audio: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined Joseph Salisbury
2014-06-18 17:14 ` [Trusty][SRU][PATCH 1/1] " Joseph Salisbury
2014-06-18 17:14 ` Joseph Salisbury
2014-06-18 17:14 ` Joseph Salisbury
2014-06-18 17:43 ` [v3.13.y][SRU][PATCH 0/1] " Greg KH
2014-06-18 17:42 ` Joseph Salisbury [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-18 17:14 Joseph Salisbury
2014-06-18 17:14 Joseph Salisbury
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=53A1CF7A.2050009@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=eldad@fogrefinery.com \
--cc=greg@kroah.com \
--cc=kamal.mostafa@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tim.gardner@canonical.com \
--cc=tiwai@suse.de \
/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.