From: Matthew Wilcox <willy@infradead.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Julia Lawall <julia.lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH v3] Documentation: Coccinelle: fix various typos etc.
Date: Thu, 2 Jul 2020 12:52:50 +0100 [thread overview]
Message-ID: <20200702115250.GX25523@casper.infradead.org> (raw)
In-Reply-To: <63450b02-93f1-1ea0-9e39-c5bb14086ce2@web.de>
On Thu, Jul 02, 2020 at 08:56:24AM +0200, Markus Elfring wrote:
> …
> > +++ linux-next-20200629/Documentation/dev-tools/coccinelle.rst
> …
> > @@ -260,13 +260,13 @@ If not using the kernel's coccicheck tar
> …
> > -We help Coccinelle when used against Linux with a set of sensible defaults
> > +We help Coccinelle when used against Linux with a set of sensible default
> > options for Linux with our own Linux .cocciconfig. This hints to coccinelle
>
> Another small wording adjustment:
> … These hints …
That would be an incorrect adjustment. Unfortunately, you snipped the
rest of the sentence that puts those two words in context. Basically it's
shorter for "By doing this, we hint to coccinelle" rather than "These
things are hints to coccinelle"
next prev parent reply other threads:[~2020-07-02 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 19:17 [PATCH v3] Documentation: Coccinelle: fix various typos etc Randy Dunlap
2020-07-01 19:26 ` [Cocci] " Julia Lawall
2020-07-02 6:56 ` Markus Elfring
2020-07-02 11:52 ` Matthew Wilcox [this message]
2020-07-05 20:06 ` Jonathan Corbet
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=20200702115250.GX25523@casper.infradead.org \
--to=willy@infradead.org \
--cc=Gilles.Muller@lip6.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=julia.lawall@lip6.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=rdunlap@infradead.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