From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] intro: trivial: remove an unnecessary dot
Date: Mon, 25 Jan 2016 16:58:00 -0800 [thread overview]
Message-ID: <20160126005800.GG4503@linux.vnet.ibm.com> (raw)
In-Reply-To: <1453709567-9156-1-git-send-email-sj38.park@gmail.com>
On Mon, Jan 25, 2016 at 05:12:47PM +0900, SeongJae Park wrote:
> There is an unnecessary dot that seemed to be inserted by trivial
> mistake. This commit just removes the dot.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good catch, applied!
Thanx, Paul
> ---
> intro/intro.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/intro/intro.tex b/intro/intro.tex
> index fc5a51e..0a8ecb7 100644
> --- a/intro/intro.tex
> +++ b/intro/intro.tex
> @@ -332,7 +332,7 @@ This change in focus is due to the fact that, although Moore's Law
> continues to deliver increases in transistor density, it has ceased to
> provide the traditional single-threaded performance increases.
> This can be seen in
> -Figure~\ref{fig:intro:Clock-Frequency Trend for Intel CPUs}.\footnote{
> +Figure~\ref{fig:intro:Clock-Frequency Trend for Intel CPUs}\footnote{
> This plot shows clock frequencies for newer CPUs theoretically
> capable of retiring one or more instructions per clock, and MIPS
> (millions of instructions per second, usually from the old
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
prev parent reply other threads:[~2016-01-26 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 8:12 [PATCH] intro: trivial: remove an unnecessary dot SeongJae Park
2016-01-26 0:58 ` Paul E. McKenney [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=20160126005800.GG4503@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.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