From: James Morse <james.morse@arm.com>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Fenghua Yu <fenghua.yu@intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/resctrl: Don't stop walking closids when a locksetup group is found
Date: Fri, 7 Jun 2019 10:39:46 +0100 [thread overview]
Message-ID: <fe2ceae9-9aeb-bad5-ed24-ca80f0297cf3@arm.com> (raw)
In-Reply-To: <20190606130802.DD95D20684@mail.kernel.org>
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
next prev parent reply other threads:[~2019-06-07 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 17:25 [PATCH v2] x86/resctrl: Don't stop walking closids when a locksetup group is found James Morse
[not found] ` <20190606130802.DD95D20684@mail.kernel.org>
2019-06-07 9:39 ` James Morse [this message]
2019-06-12 12:26 ` [tip:x86/urgent] " tip-bot for James Morse
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=fe2ceae9-9aeb-bad5-ed24-ca80f0297cf3@arm.com \
--to=james.morse@arm.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=x86@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