Linux-Doc Archive on lore.kernel.org
 help / color / Atom feed
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: [PATCH v2] Documentation: Coccinelle: fix typos and command example
Date: Tue, 30 Jun 2020 14:23:10 +0200
Message-ID: <c2c1dec0-2bd1-b0e2-1aa4-38d0e954d5ba@web.de> (raw)
In-Reply-To: <0616dd0c-bb86-be2b-3dc6-1c695a92c3ca@infradead.org>

…
> +++ linux-next-20200629/Documentation/dev-tools/coccinelle.rst
…> @@ -177,13 +177,13 @@ For example, to check drivers/net/wirele
>  To apply Coccinelle on a file basis, instead of a directory basis, the
>  following command may be used::
>
> -    make C=1 CHECK="scripts/coccicheck"
> +    make C=1 CHECK="scripts/coccicheck" path/to/file.c

I would like to clarify further software design aspects around such make functionality.

We might stumble on different interpretations according to the wording “file basis”.
Do you find a message like “make: Nothing to be done for 'path/to/file.c'.” interesting then?

* Would you like to add any links for information around the support for
  source code checkers?
  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Makefile?id=7c30b859a947535f2213277e827d7ac7dcff9c84#n198

* How do you think about to enclose the path for the shown parameter
  by single quotes instead of double quotes?

* Can such path specifications become more interesting occasionally
  if also an other file extension would be chosen than “.c”?
  Would you like to achieve any software extensions around suffix rules?

Regards,
Markus

  parent reply index

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 21:16 Randy Dunlap
2020-06-30  8:04 ` Markus Elfring
2020-06-30 12:23 ` Markus Elfring [this message]
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
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
2020-07-01 15:29 ` [Cocci] [PATCH v2] " Julia Lawall
2020-07-01 16:06   ` 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=c2c1dec0-2bd1-b0e2-1aa4-38d0e954d5ba@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

Linux-Doc Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-doc/0 linux-doc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-doc linux-doc/ https://lore.kernel.org/linux-doc \
		linux-doc@vger.kernel.org
	public-inbox-index linux-doc

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-doc


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git