All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Sun <yi.y.sun@linux.intel.com>
To: xen-devel@lists.xenproject.org
Cc: Yi Sun <yi.y.sun@linux.intel.com>,
	andrew.cooper3@citrix.com, boris.ostrovsky@oracle.com,
	wei.liu2@citrix.com, jbeulich@suse.com
Subject: [Patch for staging 1/2] docs: remove a special character to avoid html creation error.
Date: Fri,  4 Aug 2017 17:29:36 +0800	[thread overview]
Message-ID: <1501838977-63404-1-git-send-email-yi.y.sun@linux.intel.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1626 bytes --]

The '®' (a special character) may cause html document creation
failure. So remove it from the feature document.

Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
---
 docs/features/intel_psr_cat_cdp.pandoc | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/features/intel_psr_cat_cdp.pandoc b/docs/features/intel_psr_cat_cdp.pandoc
index acf877b..04fb256 100644
--- a/docs/features/intel_psr_cat_cdp.pandoc
+++ b/docs/features/intel_psr_cat_cdp.pandoc
@@ -1,5 +1,5 @@
 % Intel Cache Allocation Technology and Code and Data Prioritization Features
-% Revision 1.15
+% Revision 1.16
 
 \clearpage
 
@@ -438,7 +438,7 @@ N/A
 
 # References
 
-"INTEL® RESOURCE DIRECTOR TECHNOLOGY (INTEL® RDT) ALLOCATION FEATURES" [Intel® 64 and IA-32 Architectures Software Developer Manuals, vol3](http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html)
+"INTEL RESOURCE DIRECTOR TECHNOLOGY (INTEL RDT) ALLOCATION FEATURES" [Intel 64 and IA-32 Architectures Software Developer Manuals, vol3](http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html)
 
 # History
 
@@ -468,4 +468,7 @@ Date       Revision Version  Notes
                              1. Fix a typo.
 2017-08-01 1.15     Xen 4.10 Changes:
                              1. Add 'alt_type' in 'feat_props' structure.
+2017-08-04 1.16     Xen 4.10 Changes:
+                             1. Remove special character which may cause
+                                html creation failure.
 ---------- -------- -------- -------------------------------------------
-- 
1.9.1



[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2017-08-04  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  9:29 Yi Sun [this message]
2017-08-04  9:29 ` [Patch for staging 2/2] x86: remove an ASSERT to avoid crash when destroy a domain Yi Sun
2017-08-04 16:49   ` Jan Beulich
2017-08-05  1:26   ` [PATCH] " Yi Sun
2017-08-06  9:34     ` Jan Beulich
2017-08-07  1:21       ` Yi Sun
2017-08-07  1:50   ` [Patch for staging 2/2] x86: adjust place of " Yi Sun
2017-08-07  7:06     ` Jan Beulich
2017-08-07 10:19     ` Wei Liu
2017-08-07 10:48       ` Wei Liu
2017-08-04 11:08 ` [Patch for staging 1/2] docs: remove a special character to avoid html creation error Wei Liu

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=1501838977-63404-1-git-send-email-yi.y.sun@linux.intel.com \
    --to=yi.y.sun@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jbeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.