From: Sasha Levin <sashal@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: wanghuiqiang@huawei.com, gregkh@linuxfoundation.org,
catalin.marinas@arm.com, guohanjun@huawei.com, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linuxarm@huawei.com, linux-acpi@vger.kernel.org,
rrichter@marvell.com, jeremy.linton@arm.com,
sudeep.holla@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org, lenb@kernel.org
Subject: Re: [PATCH for-stable-5.3 1/2] ACPI/PPTT: Add support for ACPI 6.3 thread flag
Date: Tue, 15 Oct 2019 18:04:39 -0400 [thread overview]
Message-ID: <20191015220439.GQ31224@sasha-vm> (raw)
In-Reply-To: <635a839b-bc1e-37ab-bd47-a554acc9b282@huawei.com>
On Tue, Oct 15, 2019 at 09:16:13AM +0100, John Garry wrote:
>On 15/10/2019 00:29, Sasha Levin wrote:
>>On Mon, Oct 14, 2019 at 07:56:01PM +0800, John Garry wrote:
>>>From: Jeremy Linton <jeremy.linton@arm.com>
>>>
>>>Commit bbd1b70639f785a970d998f35155c713f975e3ac upstream.
>>>
>>>ACPI 6.3 adds a flag to the CPU node to indicate whether
>>>the given PE is a thread. Add a function to return that
>>>information for a given linux logical CPU.
>>>
>>>Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
>>>Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
>>>Reviewed-by: Robert Richter <rrichter@marvell.com>
>>>Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>>Signed-off-by: Will Deacon <will@kernel.org>
>>>Signed-off-by: John Garry <john.garry@huawei.com>
>>
>>How far back should these patches be backported?
>>
>
>Hi Sasha,
>
>This patchset is for 5.3, and I sent a separate patchset for 4.19,
>since the backport is a little different and required some hand
>modification -
>
>https://lore.kernel.org/linux-arm-kernel/1571046986-231263-1-git-send-email-john.garry@huawei.com/.
>4.19 is as far back as we want.
>
>Please note that the patches in this 5.3 series are relevant for 5.2
>also, but since 5.2 is EOL, I didn't mention it. We did test 5.2, so
>you can add there also.
>
>Please let me know if any more questions.
I've queued this and the 4.19 patches, thanks!
--
Thanks,
Sasha
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-15 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:56 [PATCH for-stable-5.3 0/3] ACPI, arm64: Backport for ACPI PPTT 6.3 thread flag John Garry
2019-10-14 11:56 ` [PATCH for-stable-5.3 1/2] ACPI/PPTT: Add support for ACPI " John Garry
2019-10-14 23:29 ` Sasha Levin
2019-10-15 8:16 ` John Garry
2019-10-15 22:04 ` Sasha Levin [this message]
2019-10-14 11:56 ` [PATCH for-stable-5.3 2/2] arm64: topology: Use PPTT to determine if PE is a thread John Garry
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=20191015220439.GQ31224@sasha-vm \
--to=sashal@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=jeremy.linton@arm.com \
--cc=john.garry@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=rrichter@marvell.com \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=wanghuiqiang@huawei.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).