From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com,
gavin.hindman@intel.com, jithu.joseph@intel.com,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V2] x86/intel_rdt: Ensure usage of CPUs are locked while needed
Date: Tue, 11 Dec 2018 21:58:28 +0100 [thread overview]
Message-ID: <20181211205828.GS27375@zn.tnic> (raw)
In-Reply-To: <10fef6af-785e-c76f-d89b-ec115dcf460a@intel.com>
On Tue, Dec 11, 2018 at 12:51:12PM -0800, Reinette Chatre wrote:
> I really appreciate your patience.
That goes both ways. Thx. :-)
> That subject line matches exactly the goal of this patch. Thank you very
> much. Would you prefer that I send a new version with this subject line
> or would you rather make the change yourself while applying this patch?
Nah, no need. I'll fix them up.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-12-11 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 21:21 [PATCH V2] x86/intel_rdt: Ensure usage of CPUs are locked while needed Reinette Chatre
2018-12-11 12:34 ` Borislav Petkov
2018-12-11 18:33 ` Reinette Chatre
2018-12-11 18:50 ` Borislav Petkov
2018-12-11 19:02 ` Reinette Chatre
2018-12-11 20:43 ` Borislav Petkov
2018-12-11 20:51 ` Reinette Chatre
2018-12-11 20:58 ` Borislav Petkov [this message]
2018-12-11 21:13 ` [tip:x86/urgent] x86/intel_rdt: Ensure a CPU remains online for the region's pseudo-locking sequence tip-bot for Reinette Chatre
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=20181211205828.GS27375@zn.tnic \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=gavin.hindman@intel.com \
--cc=hpa@zytor.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).