Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754476AbaFUTsl (ORCPT ); Sat, 21 Jun 2014 15:48:41 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:34245 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752558AbaFUTsj (ORCPT ); Sat, 21 Jun 2014 15:48:39 -0400 X-Sasl-enc: 9G7avVJakkJTwxK7XU4lRdoc0sqnIotZLAouwmdhHxWW 1403380118 Date: Sat, 21 Jun 2014 12:48:27 -0700 From: Greg KH To: Ben Hutchings Cc: Joseph Salisbury , kamal.mostafa@canonical.com, luis.henriques@canonical.com, jslaby@suse.cz, clm@fb.com, jbacik@fb.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [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 Message-ID: <20140621194827.GA5128@kroah.com> References: <1403142759.23472.28.camel@deadeye.wl.decadent.org.uk> <53A4515C.8090103@canonical.com> <53A47BC4.8040406@canonical.com> <1403352353.23472.67.camel@deadeye.wl.decadent.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1403352353.23472.67.camel@deadeye.wl.decadent.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jun 21, 2014 at 01:05:53PM +0100, Ben Hutchings wrote: > On Fri, 2014-06-20 at 14:21 -0400, Joseph Salisbury wrote: > [...] > > I looked at this some more. It seems like my v2 backport may be the > > most suitable for the releases mentioned in the subject line, but I'd > > like to get additional feedback. > > > > The lines added by commit a5065eb just get removed by commit b7a77235. > > Also, if I apply commit a5065eb, it will also require a backport to pull > > in just a piece of code(Remove snd_printk() and add dev_dbg()) from > > another prior commit(0ba41d9). No backport would be needed at all if I > > cherry-pick 0ba41d9, but that commit seems to have too may changes for a > > stable release. > > Keep the changes squashed together if you like, but do include both > commit hashes and commit messages. No, I don't want to see "squashed together" patches, please keep them as close to the original patch as possible. It saves time in the long run, trust me... greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/