On 01/09/2023 20:23, Greg Kroah-Hartman wrote:
On Fri, Sep 01, 2023 at 06:38:14PM +0100, Suzuki K Poulose wrote:
On 01/09/2023 16:47, Greg Kroah-Hartman wrote:
On Fri, Sep 01, 2023 at 12:15:51PM +0100, Suzuki K Poulose wrote:
Hi Greg
I have a question for you w.r.t pushing this series [0]. This involved some changes to the ARM PMU ACPI stub code, for parsing the ACPI tables to detect TRBE (managed via CoreSight drivers).
The ARM PMU ACPI stub is maintained by Will and he tried to queue this in, but there was a conflict [1] with the CoreSight branch and hence he dropped the coresight changes, keeping the base changes.
His questions in the thread above were clariried [2] and Anshuman has posted the "coresight" changes alone [3].
Now, I have already sent a pull request for v6.6. Do you think I can send a pull request with the remaining changes from Anshuman ?
Has any of this been in linux-next yet? If not, then 6.6 is not going to happen, sorry.
As mentioned they were in shortly, but dropped due to the conflict with CoreSight tree.
Then the code can't be merged into 6.6-rc1.
If it has been in linux-next, then what's the issue?
If so, what do you recommend ? The dependent patches are already queued via Will's tree and merged by Linus [4]
I am happy to wait for the next cycle, if this is inconvenient for you.
I can't take anything new for my trees until after 6.6-rc1 is out, neither can anyone else.
And if the dependancies are going to go in for 6.6-rc1, then what's the issue?
It is just that the functionality was split and there is something in in 6.6-rc1, which nobody is consuming, unless these two patches come in. Do you recommend sending them for v6.6 ? Or queue them for v6.7 ?
Queue for 6.7 please.
Thanks, will do.
Suzuki
-
Suzuki K Poulose