stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	stable@vger.kernel.org, "Jin, Yao" <yao.jin@intel.com>,
	"Liang, Kan" <kan.liang@intel.com>
Subject: Re: perf: Support uncore in 4.9.112
Date: Wed, 8 Aug 2018 10:40:49 +0200	[thread overview]
Message-ID: <20180808084049.GA24734@kroah.com> (raw)
In-Reply-To: <7e63c7da-e883-04ab-abf7-6ccf87ff3a70@linux.intel.com>

On Wed, Aug 08, 2018 at 03:37:54PM +0800, Jin, Yao wrote:
>  182 files changed, 97061 insertions(+), 159 deletions(-)

Look at that, 97 thousand lines added :(

Yes, almost everything here is in tools/perf/ which leads me to ask why
can't you just run a newer kernel's perf on 4.9 and have all of this
support?  Why do you need these in the stable 4.9 release in order for
this to work properly?

And as you can see here, that's really way too big for a stable kernel
release, how can you justify it based on the stable kernel rules?

thanks,

greg k-h

  reply	other threads:[~2018-08-08 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  0:41 perf: Support uncore in 4.9.112 Jin, Yao
2018-07-18  9:29 ` Greg KH
2018-07-18 17:09   ` Andi Kleen
2018-07-18 17:39     ` Greg KH
2018-07-19  4:43       ` Jin, Yao
2018-08-06  0:46       ` Jin, Yao
2018-08-07 13:09         ` Greg KH
2018-08-08  0:58           ` Jin, Yao
2018-08-08  6:40             ` Greg KH
2018-08-08  7:37               ` Jin, Yao
2018-08-08  8:40                 ` Greg KH [this message]
2018-08-09  5:59                   ` Jin, Yao
2018-08-09  7:47                     ` Greg KH
2018-08-09  8:07                       ` Jin, Yao

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=20180808084049.GA24734@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ak@linux.intel.com \
    --cc=kan.liang@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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).