From: Markus Elfring <Markus.Elfring@web.de>
To: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <michal.lkml@markovi.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [v2] Documentation: Coccinelle: fix typos and command example
Date: Wed, 01 Jul 2020 15:15:07 +0000 [thread overview]
Message-ID: <65db3f88-1ac8-374d-e3fe-2ea0970ffd67@web.de> (raw)
In-Reply-To: <34065299-03cf-5b62-db37-0acc9830be72@infradead.org>
>> Would you like to integrate any more details from the running patch review?
>
> I am satisfied with the current patch.
I got an other software development impression.
> No doubt that any documentation can be improved, almost ad infinitum,
> but I'm not trying to do that.
Do we stumble on a target conflict according to a specific technical detail?
How do you think about to compare source code analysis results
from programs like “sparse” and “spatch” (by the mentioned make command)?
Regards,
Markus
next prev parent reply other threads:[~2020-07-01 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0616dd0c-bb86-be2b-3dc6-1c695a92c3ca@infradead.org>
2020-06-30 8:04 ` [PATCH v2] Documentation: Coccinelle: fix typos and command example Markus Elfring
2020-06-30 12:23 ` Markus Elfring
2020-06-30 15:11 ` Randy Dunlap
2020-07-01 11:56 ` Markus Elfring
2020-07-01 13:20 ` Randy Dunlap
2020-07-01 13:32 ` [v2] " Markus Elfring
2020-07-01 14:52 ` Randy Dunlap
2020-07-01 15:02 ` Markus Elfring
2020-07-01 15:07 ` Randy Dunlap
2020-07-01 15:15 ` Markus Elfring
2020-07-01 15:19 ` Jonathan Corbet
2020-07-01 15:23 ` Markus Elfring
2020-07-01 15:15 ` Markus Elfring [this message]
2020-07-01 15:19 ` Randy Dunlap
2020-07-01 15:32 ` Markus Elfring
2020-07-01 17:32 ` Markus Elfring
2020-07-01 19:15 ` Randy Dunlap
2020-07-01 20:10 ` Markus Elfring
[not found] ` <alpine.DEB.2.22.394.2007012232510.2540@hadrien>
2020-07-02 6:01 ` Markus Elfring
2020-07-02 8:22 ` Markus Elfring
2020-07-02 0:08 ` Matthew Wilcox
2020-07-02 5:40 ` Julia Lawall
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=65db3f88-1ac8-374d-e3fe-2ea0970ffd67@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--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 \
--cc=yamada.masahiro@socionext.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).