All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: mikulas@twibright.com, torvalds@linux-foundation.org,
	stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV instead" has been added to the 3.10-stable tree
Date: Fri, 31 Jul 2015 13:03:33 -0700	[thread overview]
Message-ID: <20150731200333.GA15198@kroah.com> (raw)
In-Reply-To: <1438371755.19675.136.camel@perches.com>

On Fri, Jul 31, 2015 at 12:42:35PM -0700, Joe Perches wrote:
> On Fri, 2015-07-31 at 12:37 -0700, gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV instead
> > 
> > to the 3.10-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> While I know this patch reduces some code and text,
> it's not correcting any defect in the code, it's
> only a minor optimization.
> 
> Is it really appropriate for stable?

I agree, why was it marked that way?  I assumed it was due to the patch
after it needed it, but maybe not.  Any objection to me just dropping
it?

thanks,

greg k-h

  reply	other threads:[~2015-07-31 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 19:37 Patch "hpfs: hpfs_error: Remove static buffer, use vsprintf extension %pV instead" has been added to the 3.10-stable tree gregkh
2015-07-31 19:42 ` Joe Perches
2015-07-31 20:03   ` Greg KH [this message]
2015-07-31 20:35     ` Joe Perches
2015-07-31 21:27       ` Mikulas Patocka
2015-07-31 22:12         ` Joe Perches

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=20150731200333.GA15198@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=mikulas@twibright.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.