From: Markus Elfring <Markus.Elfring@web.de>
To: Ricardo Ribalda <ribalda@google.com>,
cocci@inria.fr, Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [cocci] linux-next: virtual rule report not supported
Date: Thu, 23 Jan 2025 13:05:54 +0100 [thread overview]
Message-ID: <07da64ca-e645-4a29-bc21-c3065ad5a3c4@web.de> (raw)
In-Reply-To: <CANiDSCvLCaMdJVSMahNgg1UQMh3naoTrWGh=9+4p8pePWyLStg@mail.gmail.com>
> While trying out linux-next I have hit an error in cocci:
>
> $make coccicheck M="$dir" MODE=report
> ...
> /usr/bin/spatch -D report --no-show-diff --very-quiet --cocci-file
> /workdir/scripts/coccinelle/misc/secs_to_jiffies.cocci --patch
> /workdir --dir . -I /workdir/arch/x86/include -I
> /workdir/arch/x86/include/generated -I /workdir/include -I
> /workdir/include -I /workdir/arch/x86/include/uapi -I
> /workdir/arch/x86/include/generated/uapi -I /workdir/include/uapi -I
> /workdir/include/generated/uapi --include
> /workdir/include/linux/compiler-version.h --include
> /workdir/include/linux/kconfig.h --jobs 64 --chunksize 1
> virtual rule report not supported
> coccicheck failed
> make[1]: Leaving directory '/workdir/drivers/media'
> make[2]: *** [/workdir/Makefile:2094: coccicheck] Error 255
> make[1]: *** [/workdir/Makefile:251: __sub-make] Error 2
> make: *** [Makefile:251: __sub-make] Error 2
>
> Deleting scripts/coccinelle/misc/secs_to_jiffies.cocci "works"
Would you like to increase the development attention for better support
of involved operation modes?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/dev-tools/coccinelle.rst?h=v6.13#n71
Regards,
Markus
parent reply other threads:[~2025-01-23 12:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANiDSCvLCaMdJVSMahNgg1UQMh3naoTrWGh=9+4p8pePWyLStg@mail.gmail.com>]
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=07da64ca-e645-4a29-bc21-c3065ad5a3c4@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=cocci@inria.fr \
--cc=eahariha@linux.microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ribalda@google.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