From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Michal Marek <michal.lkml@markovi.net>,
linux-doc@vger.kernel.org, Nicolas Palix <nicolas.palix@imag.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@lip6.fr>,
Markus Elfring <Markus.Elfring@web.de>,
Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [v2] Documentation: Coccinelle: fix typos and command example
Date: Thu, 2 Jul 2020 01:08:43 +0100 [thread overview]
Message-ID: <20200702000843.GV25523@casper.infradead.org> (raw)
In-Reply-To: <dfa2ed9f-fe68-58d1-c3d0-ac436f9bee09@infradead.org>
On Wed, Jul 01, 2020 at 07:52:58AM -0700, Randy Dunlap wrote:
> On 7/1/20 6:32 AM, Markus Elfring wrote:
> >>> How do you think about to use the following command variant
> >>> for the adjustment of the software documentation?
> >>>
> >>> + make C=1 CHECK='scripts/coccicheck' 'path/to/file.o'
> >>
> >> I don't understand the reason for that change...
>
> IOW, your "patch" needs justification and/or explanation. It was missing that info.
What Markus is trying so completely ineptly to say is that
make C=1 CHECK=scripts/coccicheck path/to/file.c
doesn't work. You need to use the .o suffix to check the .c file.
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-07-02 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 21:16 [Cocci] [PATCH v2] Documentation: Coccinelle: fix typos and command example Randy Dunlap
[not found] ` <c2c1dec0-2bd1-b0e2-1aa4-38d0e954d5ba@web.de>
2020-06-30 15:11 ` Randy Dunlap
[not found] ` <2a3940de-6a81-1aff-8109-53c1c5a6aa1b@web.de>
2020-07-01 13:20 ` Randy Dunlap
[not found] ` <2f80fb10-dc7f-29be-dc3e-2715f8bafc6d@web.de>
2020-07-01 14:52 ` [Cocci] [v2] " Randy Dunlap
[not found] ` <648d287e-3636-1858-1439-103d317f8571@web.de>
2020-07-01 15:07 ` Randy Dunlap
[not found] ` <65db3f88-1ac8-374d-e3fe-2ea0970ffd67@web.de>
2020-07-01 15:19 ` Randy Dunlap
[not found] ` <bd4033cd-f564-0414-4dbf-4ff58f841648@web.de>
2020-07-01 19:15 ` Randy Dunlap
2020-07-02 0:08 ` Matthew Wilcox [this message]
2020-07-02 5:40 ` Julia Lawall
2020-07-01 15:29 ` [Cocci] [PATCH v2] " 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=20200702000843.GV25523@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=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 \
/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).