From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: William Dauchy <william@gandi.net>
Cc: stable@vger.kernel.org, linux@roeck-us.net,
satoru.takeuchi@gmail.com, shuah.kh@samsung.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH 3.12 00/96] 3.12.30-stable review
Date: Fri, 10 Oct 2014 04:40:47 -0700 [thread overview]
Message-ID: <20141010114047.GB32429@kroah.com> (raw)
In-Reply-To: <CAJ75kXb-mmrW9n51O19rM4xz1i_qTBjzAkOzfY5brWW4TEig1A@mail.gmail.com>
On Fri, Oct 10, 2014 at 09:32:45AM +0200, William Dauchy wrote:
> Hi stable release team,
>
> On Wed, Oct 1, 2014 at 10:57 AM, Jiri Slaby <jslaby@suse.cz> wrote:
> > This one is special. First, it is rounded (30). Second, most of the
> > patches are performance improvements. They are coming from SUSE
> > Enterprise Linux and all are backed by proper testing and performance
> > measurements. All this patchset was prepared and sent by Mel Gorman
> > with a support of other patchers from SUSE. Thanks to all of them.
>
> I'm just wondering if 3.10.x and 3.14.x are going to benefit from
> these performance improvement patches as well.
The last 3.14.x release had a bunch of these patches already in them,
with more to come in future releases, so yes, 3.14.x is going to benefit
from it, and you didn't even notice :)
But 3.10 will probably not, it's been just too long for that kernel
release, sorry, major mm changes like this isn't something I'm willing
to do at this point in time.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2014-10-10 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 8:57 [PATCH 3.12 00/96] 3.12.30-stable review Jiri Slaby
2014-10-01 16:23 ` Guenter Roeck
2014-10-10 8:17 ` Jiri Slaby
2014-10-01 16:24 ` Shuah Khan
2014-10-03 11:40 ` Satoru Takeuchi
2014-10-10 7:32 ` William Dauchy
2014-10-10 11:40 ` Greg Kroah-Hartman [this message]
2014-10-10 11:45 ` William Dauchy
2014-10-10 11:42 ` Holger Hoffstätte
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=20141010114047.GB32429@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=satoru.takeuchi@gmail.com \
--cc=shuah.kh@samsung.com \
--cc=stable@vger.kernel.org \
--cc=william@gandi.net \
/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).