From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [cocci] Improving output for single characters (with SmPL)?
Date: Sat, 1 Aug 2026 14:00:26 +0200 [thread overview]
Message-ID: <47b1a35d-8a88-4944-af8c-077925936106@web.de> (raw)
In-Reply-To: <9e187875-e472-911-c280-59dff6b7c80@inria.fr>
>>> Markus_Elfring@Sonne:/home/altes_Heim2/elfring/Projekte/Linux/next-analyses> grep 'diff -u -p a/netlink_dumper.h b/netlink_dumper.h' /home/altes_Heim2/elfring/Projekte/Bau/Linux/scripts/Coccinelle/tuning1/next/20260721/use_fputc-bpftool-2.diff | wc -l
>>> 2
>>
>> How can the generation of duplicate difference output be avoided here
>> for other SmPL script variations?
>
> I don't know the details o what you are doing,
How does such a feedback fit to provided information?
> but if you have duplicated
> output about herder files, it would be because the header file is included
> in other files.
Duplicate difference hunks are not produced in all test cases.
Can you reproduce unexpected software behaviour also in your test environment?
Regards,
Markus
next prev parent reply other threads:[~2026-08-01 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 17:03 Markus Elfring
2026-07-23 19:26 ` Markus Elfring
2026-07-24 9:02 ` Markus Elfring
2026-08-01 8:10 ` Markus Elfring
2026-08-01 8:18 ` Julia Lawall
2026-08-01 12:00 ` Markus Elfring [this message]
2026-08-02 10:06 ` [cocci] " Markus Elfring
2026-08-03 5:40 ` [cocci] Improving parallel data processing for hierarchical structures? 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=47b1a35d-8a88-4944-af8c-077925936106@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®