From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] formal: Trivial typo fixes
Date: Tue, 19 Jul 2016 08:17:35 -0700 [thread overview]
Message-ID: <20160719151735.GW7094@linux.vnet.ibm.com> (raw)
In-Reply-To: <6e78783e-7f09-931d-5981-ad11af4bd7b5@gmail.com>
On Wed, Jul 20, 2016 at 12:08:29AM +0900, Akira Yokosawa wrote:
> On 2016/07/19 23:42 +0900, Akira Yokosawa wrote:
>
> Hi Paul,
>
> These are typos I noticed while reading recently updated part in "formal/formal.tex".
>
> > Furthermore, although the L4 microkernel is a large software
> > artifact from the viewpoint of formal verification, it is tiny
> > - compared to the a great number of projects, including LLVM,
> > + compared to a great number of projects, including LLVM,
>
> Here, "the" and "a" are redundant. I removed "the", because I have no idea
> how many projects are there in this context.
>
> > gcc, the Linux kernel, Hadoop, MongoDB, and a great many others.
> >
> > Although formal verification is finally starting to show some
> > @@ -171,4 +171,4 @@ All else being equal, a simpler implementation is much better than
> > a mechanical proof for a complex implementation!
> >
> > And the open challenge to those working on formal verification techniques
> > -and systems is prove this summary wrong!
> > +and systems is to prove this summary wrong!
> >
>
> This seems a trivial one.
Agreed on both, pulled and pushed. And thank you for your careful
review and the fixes!
Thanx, Paul
next prev parent reply other threads:[~2016-07-19 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:42 [PATCH] formal: Trivial typo fixes Akira Yokosawa
2016-07-19 15:08 ` Akira Yokosawa
2016-07-19 15:17 ` Paul E. McKenney [this message]
2016-07-19 15:10 ` Paul E. McKenney
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=20160719151735.GW7094@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--cc=perfbook@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox