public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, andrew.brown@intel.com,
	dave.hansen@linux.intel.com, Ian Rogers <irogers@google.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Hector Martin <marcan@marcan.st>, Marc Zyngier <maz@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH stable 6.6 and 6.7 2/2] perf top: Uniform the event name for the hybrid machine
Date: Fri, 29 Mar 2024 09:16:09 -0400	[thread overview]
Message-ID: <ed2715c2-d572-44c9-8b6c-0f897e5c8108@linux.intel.com> (raw)
In-Reply-To: <2024032918-spruce-sapling-c829@gregkh>

Hi Greg,

On 2024-03-29 9:09 a.m., Greg KH wrote:
> On Fri, Mar 08, 2024 at 07:12:39AM -0800, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> [The patch set is to fix the perf top failure on all Intel hybrid
>> machines. Without the patch, the default perf top command is broken.
>>
>> I have verified that the patches on both stable 6.6 and 6.7. They can
>> be applied to stable 6.6 and 6.7 tree without any modification as well.
>>
>> Please consider to apply them to stable 6.6 and 6.7. Thanks]
> 
> Already in the 6.6.23 and 6.7.11 releases.
> 

Thanks. I see this one (2/2) is merged.
Could you please also apply the first patch (1/2) as well? Without the
first one, the perf top still fails.

Thanks,
Kan

> thanks,
> 
> greg k-h

  reply	other threads:[~2024-03-29 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 15:12 [PATCH stable 6.6 and 6.7 1/2] perf top: Use evsel's cpus to replace user_requested_cpus kan.liang
2024-03-08 15:12 ` [PATCH stable 6.6 and 6.7 2/2] perf top: Uniform the event name for the hybrid machine kan.liang
2024-03-29 13:09   ` Greg KH
2024-03-29 13:16     ` Liang, Kan [this message]
2024-03-29 13:25       ` 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=ed2715c2-d572-44c9-8b6c-0f897e5c8108@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@redhat.com \
    --cc=andrew.brown@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=irogers@google.com \
    --cc=marcan@marcan.st \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=namhyung@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