From: Markus Elfring <Markus.Elfring@web.de>
To: linux-doc@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Julia Lawall <julia.lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <masahiroy@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Documentation: Coccinelle: Checking information aroun =?UTF-8?B?ZCB0aGUgbWFrZSBwYXJh
Date: Fri, 03 Jul 2020 19:21:51 +0000 [thread overview]
Message-ID: <e546930c-0022-c0ea-059f-0c5ec782b5ab@web.de> (raw)
Hello,
I have taken another look also at places from two information sources.
A)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Makefile?id=cdd3bb54332f82295ed90cd0c09c78cd0c0ee822#n201
“…
# Use 'make C=1' to enable checking of only re-compiled files.
# Use 'make C=2' to enable checking of *all* source files, regardless
# of whether they are re-compiled or not.
…”
B)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?id=cdd3bb54332f82295ed90cd0c09c78cd0c0ee822#n182
“…
To check only newly edited code, use the value 2 for the C flag, i.e.::
…”
How good do these description variants fit together?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: linux-doc@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Julia Lawall <julia.lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <masahiroy@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Documentation: Coccinelle: Checking information around the make parameter “C=2”
Date: Fri, 3 Jul 2020 21:21:51 +0200 [thread overview]
Message-ID: <e546930c-0022-c0ea-059f-0c5ec782b5ab@web.de> (raw)
Hello,
I have taken another look also at places from two information sources.
A)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Makefile?id=cdd3bb54332f82295ed90cd0c09c78cd0c0ee822#n201
“…
# Use 'make C=1' to enable checking of only re-compiled files.
# Use 'make C=2' to enable checking of *all* source files, regardless
# of whether they are re-compiled or not.
…”
B)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?id=cdd3bb54332f82295ed90cd0c09c78cd0c0ee822#n182
“…
To check only newly edited code, use the value 2 for the C flag, i.e.::
…”
How good do these description variants fit together?
Regards,
Markus
next reply other threads:[~2020-07-03 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 19:21 Markus Elfring [this message]
2020-07-03 19:21 ` Documentation: Coccinelle: Checking information around the make parameter “C=2” Markus Elfring
2020-07-07 14:16 ` kbuild: Improve descriptions for the make parameter “C” Markus Elfring
2020-07-07 14:16 ` Markus Elfring
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=e546930c-0022-c0ea-059f-0c5ec782b5ab@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=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=rdunlap@infradead.org \
--cc=willy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.