From: Fenghua Yu <fenghua.yu@intel.com>
To: Xiaochen Shen <xiaochen.shen@intel.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org, x86@kernel.org,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH] x86/intel_rdt: Fix two typos in Documentation
Date: Tue, 9 May 2017 00:30:20 -0700 [thread overview]
Message-ID: <20170509073020.GA4476@linux.intel.com> (raw)
In-Reply-To: <1491498581-21735-1-git-send-email-xiaochen.shen@intel.com>
On Fri, Apr 07, 2017 at 01:09:41AM +0800, Xiaochen Shen wrote:
> Both typos are in example 3.
>
> Because cache id 0 is the only cache id, the ";" is redundant in
> "# echo "L3:0=ffc00;" > p0/schemata".
>
> And "C0" in "# echo C0 > p0/cpus" is wrong because it specifies core
> 6-7 instead of wanted core 4-7.
>
> Correct the typos to avoid confusion.
>
> Signed-off-by: Xiaochen Shen <xiaochen.shen@intel.com>
Acked-by: Fenghua Yu <fenghua.yu@intel.com>
prev parent reply other threads:[~2017-05-09 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 17:09 [PATCH] x86/intel_rdt: Fix two typos in Documentation Xiaochen Shen
2017-05-03 3:29 ` Shen, Xiaochen
2017-05-09 7:30 ` Fenghua Yu [this message]
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=20170509073020.GA4476@linux.intel.com \
--to=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xiaochen.shen@intel.com \
/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