[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140621194827.GA5128@kroah.com>
Date: Sat, 21 Jun 2014 12:48:27 -0700
From: Greg KH <greg@...ah.com>
To: Ben Hutchings <ben@...adent.org.uk>
Cc: Joseph Salisbury <joseph.salisbury@...onical.com>,
kamal.mostafa@...onical.com, luis.henriques@...onical.com,
jslaby@...e.cz, clm@...com, jbacik@...com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.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
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists