[<prev] [next>] [day] [month] [year] [list]
Message-ID: <fe2ceae9-9aeb-bad5-ed24-ca80f0297cf3@arm.com>
Date: Fri, 7 Jun 2019 10:39:46 +0100
From: James Morse <james.morse@....com>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
Fenghua Yu <fenghua.yu@...el.com>, stable@...r.kernel.org
Subject: Re: [PATCH v2] x86/resctrl: Don't stop walking closids when a
locksetup group is found
Hi,
On 06/06/2019 14:08, Sasha Levin wrote:
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: dfe9674b04ff x86/intel_rdt: Enable entering of pseudo-locksetup mode.
>
> The bot has tested the following trees: v5.1.7, v5.0.21, v4.19.48.
> v5.1.7: Failed to apply! Possible dependencies:> 7390619ab9ea ("x86/resctrl: Move per RDT domain initialization to a separate function")
>
> v5.0.21: Failed to apply! Possible dependencies:
> 7390619ab9ea ("x86/resctrl: Move per RDT domain initialization to a separate function")
That's cleanup, I don't think you want for stable. I'll do a backport.
> v4.19.48: Failed to apply! Possible dependencies:
> 2a7adf6ce643 ("x86/intel_rdt: Fix initial allocation to consider CDP")
This one changed an adjacent line.
> 723f1a0dd8e2 ("x86/resctrl: Fixup the user-visible strings")
> 7390619ab9ea ("x86/resctrl: Move per RDT domain initialization to a separate function")
> How should we proceed with this patch?
I'll come up with backports for v5.1.x/v5.0.x and v4.19.x once this reaches mainline.
Thanks,
James
Powered by blists - more mailing lists