Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>,
	       Joseph Myers <joseph@codesourcery.com>,
	Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [OBV PATCH] MPX documentation
Date: Mon, 21 Dec 2015 13:48:00 -0000	[thread overview]
Message-ID: <5678030C.6030304@redhat.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B1944507680@IRSMSX104.ger.corp.intel.com>

> From: Joseph Myers [mailto:joseph@codesourcery.com] 
> On Thu, 17 Dec 2015, Eli Zaretskii wrote:
>>> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
>>> Fix some trademarks on MPX section.
>>
>> Do we have to?
> 
> The GNU Coding Standards say "Please do not include any trademark acknowledgements in GNU software packages or documentation.".  So the patch is wrong.

Does that mean that all existing "(R)" occurrences in the documentation
should be removed?

$ grep "(R)" *
gdb.texinfo:@cindex Intel(R) Processor Trace
gdb.texinfo:Use the @dfn{Intel(R) Processor Trace} recording format.  In this
gdb.texinfo:Set the requested ring buffer size for branch tracing in Intel(R)
gdb.texinfo:that uses the btrace recording method and the Intel(R) Processor Trace
gdb.texinfo:tracing in Intel(R) Processor Trace format.
gdb.texinfo:@subsubsection Intel(R) @dfn{Memory Protection Extensions} (MPX).
gdb.texinfo:@cindex Intel(R) Memory Protection Extensions (MPX).
gdb.texinfo:For the Intel(R) Processor Trace recording format, print a list of
gdb.texinfo:Intel(R) Processor Trace packets.  For each packet, the following
gdb.texinfo:Enable branch tracing for the current thread using Intel(R) Processor Trace.
gdb.texinfo:This thread uses the @dfn{Intel(R) Processor Trace} (@acronym{Intel(R)
gdb.texinfo:The size of the @acronym{Intel(R) PT} ring buffer in bytes.
gdb.texinfo:The @samp{org.gnu.gdb.i386.mpx} is an optional feature representing Intel(R)

Thanks,
Pedro Alves


  reply	other threads:[~2015-12-21 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 13:24 Walfred Tedeschi
2015-12-17 16:19 ` Eli Zaretskii
2015-12-17 18:05   ` Joseph Myers
2015-12-18  7:48     ` Tedeschi, Walfred
2015-12-21 13:48       ` Pedro Alves [this message]
2015-12-21 15:39         ` Eli Zaretskii
2015-12-21 17:38           ` Pedro Alves
2016-01-11 11:42           ` Pedro Alves
2016-01-11 12:35             ` Tedeschi, Walfred
2016-01-11 14:07               ` Pedro Alves
2016-01-11 15:41             ` Eli Zaretskii

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=5678030C.6030304@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=walfred.tedeschi@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