From: Greg KH <greg@kroah.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: stable kernel team <stable@vger.kernel.org>
Subject: Re: Please merge perf fixes into v4.1.1
Date: Wed, 24 Jun 2015 07:47:29 -0700 [thread overview]
Message-ID: <20150624144729.GA17352@kroah.com> (raw)
In-Reply-To: <20150624134124.GA10550@gmail.com>
On Wed, Jun 24, 2015 at 03:41:24PM +0200, Ingo Molnar wrote:
>
> hi Greg,
>
> * Ingo Molnar <mingo@kernel.org> wrote:
>
> > hi Greg,
> >
> > Please merge the following upstream perf commits into v4.1.1:
> >
> > git merge 75e84ab906ef
> >
> > This will merge the following fixes:
> >
> > 2f993cf09364 ("perf: Fix ring_buffer_attach() RCU sync, again")
> > 4b36f1a4139c ("perf/x86: Add more Broadwell model numbers")
> > 6b099d9b040b ("perf/x86/intel/bts: Fix DS area sharing with x86_pmu events")
> > 1b7b938f1817 ("perf/x86/intel: Fix PMI handling for Intel PT")
> > 2c33645d366d ("perf/x86: Honor the architectural performance monitoring version")
> > 75e84ab906ef ("perf tools: Fix build breakage if prefix= is specified")
> >
> > Note: commit IDs are listed in cherry picking order, in case you want to
> > cherry-pick them.
>
> Please disregard all these sha1's for the time being, as a regression has just
> been bisected back to:
>
> 1b7b938f1817 ("perf/x86/intel: Fix PMI handling for Intel PT")
Ok, should I just ignore all of these then? Don't you want the other
patches before that one merged?
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-24 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 7:28 Please merge perf fixes into v4.1.1 Ingo Molnar
2015-06-24 13:41 ` Ingo Molnar
2015-06-24 14:47 ` Greg KH [this message]
2015-06-25 7:01 ` Ingo Molnar
2015-06-26 4:11 ` 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=20150624144729.GA17352@kroah.com \
--to=greg@kroah.com \
--cc=mingo@kernel.org \
--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