From: Greg KH <greg@kroah.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Joseph Salisbury <joseph.salisbury@canonical.com>,
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
Date: Sat, 21 Jun 2014 12:48:27 -0700 [thread overview]
Message-ID: <20140621194827.GA5128@kroah.com> (raw)
In-Reply-To: <1403352353.23472.67.camel@deadeye.wl.decadent.org.uk>
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
next prev parent reply other threads:[~2014-06-21 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 18:32 [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 Joseph Salisbury
2014-06-18 18:32 ` [v3.10.y][v3.11.y][v3.12.y][v3.13.y][v3.14.y][PATCH 1/1][V2] " 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 [this message]
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=20140621194827.GA5128@kroah.com \
--to=greg@kroah.com \
--cc=ben@decadent.org.uk \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=joseph.salisbury@canonical.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).