From: Jonathan Corbet <corbet@lwn.net>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
prarit@redhat.com, rafael.j.wysocki@intel.co,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] admin guide/pm: Admin guide for intel-speed-select
Date: Mon, 18 Nov 2019 10:58:31 -0700 [thread overview]
Message-ID: <20191118105831.5fd78335@lwn.net> (raw)
In-Reply-To: <20191118174828.GY32742@smile.fi.intel.com>
On Mon, 18 Nov 2019 19:48:28 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> On Mon, Nov 18, 2019 at 10:41:05AM -0700, Jonathan Corbet wrote:
> > On Fri, 15 Nov 2019 12:49:25 -0800
> > Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> wrote:
>
> > > Added documentation to configure servers to use Intel(R) Speed
> > > Select Technology using intel-speed-select tool.
>
> > > +=========================================================
> > > +Intel® Speed Select Technology (Intel® SST) : User Guide
> > > +=========================================================
> >
> > People give me grief when I take docs patches adding non-ascii characters.
> > Adding nearly 100 useless ® symbols seems likely to trigger that sort of
> > unicode aversion. Can I ask you, please, to take those out? There are
> > many occurrences of unadorned "Intel" in the kernel, and the world hasn't
> > ended yet.
>
> Side comment. It's really strange to hear above in 21st centure. We are living
> in Unicode times. How harm unicode characters nowadays?
In general I agree, and I have little patience for complaints about
non-ascii characters in places where they actually have value. This,
however, is not one of those places.
Thanks,
jon
next prev parent reply other threads:[~2019-11-18 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 20:49 [PATCH] admin guide/pm: Admin guide for intel-speed-select Srinivas Pandruvada
2019-11-18 10:52 ` Andy Shevchenko
2019-11-18 17:41 ` Jonathan Corbet
2019-11-18 17:48 ` Andy Shevchenko
2019-11-18 17:58 ` Jonathan Corbet [this message]
2019-11-18 22:55 ` Srinivas Pandruvada
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=20191118105831.5fd78335@lwn.net \
--to=corbet@lwn.net \
--cc=andriy.shevchenko@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rafael.j.wysocki@intel.co \
--cc=srinivas.pandruvada@linux.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;
as well as URLs for NNTP newsgroup(s).