From: Markus Elfring <Markus.Elfring@web.de>
To: Victor Gambier <victor.gambier@inria.fr>, cocci@inria.fr
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [cocci] Comparing software run time characteristics
Date: Tue, 11 Feb 2025 11:33:13 +0100 [thread overview]
Message-ID: <e01dde43-9c07-4914-ba39-224b4eccdeb0@web.de> (raw)
In-Reply-To: <e9273f8b-7e6d-4441-8681-3f9044c23257@inria.fr>
> That is not enough to narrow it down, I'll see if I can figure out something else.
* Which test criteria did you try out so far?
* Will development interests grow anyhow for more precise analyses
of questionable software behaviour?
Regards,
Markus
next prev parent reply other threads:[~2025-02-11 10:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 9:31 [cocci] possible regressions in 1.1.1 -> 1.2 Johannes Berg
2025-02-06 9:48 ` Johannes Berg
2025-02-06 9:53 ` Victor Gambier
2025-02-06 10:00 ` Johannes Berg
2025-02-06 12:36 ` Markus Elfring
2025-02-06 9:59 ` Julia Lawall
2025-02-06 10:07 ` Johannes Berg
2025-02-06 10:12 ` Johannes Berg
2025-02-06 13:34 ` Markus Elfring
2025-02-06 10:13 ` Julia Lawall
2025-02-06 10:17 ` Johannes Berg
2025-02-06 13:46 ` Markus Elfring
2025-02-06 13:00 ` Markus Elfring
2025-02-06 16:50 ` Markus Elfring
2025-02-08 11:26 ` [cocci] Checking SmPL test cases? Markus Elfring
2025-02-08 11:58 ` Julia Lawall
2025-02-08 12:51 ` Markus Elfring
2025-02-08 14:28 ` Markus Elfring
2025-02-08 15:43 ` Julia Lawall
2025-02-09 8:42 ` Markus Elfring
2025-02-07 7:43 ` [cocci] Checking software run time characteristics Markus Elfring
2025-02-07 7:55 ` Julia Lawall
2025-02-07 8:15 ` Markus Elfring
2025-02-07 8:59 ` Johannes Berg
2025-02-07 9:50 ` Markus Elfring
2025-02-11 9:58 ` [cocci] possible regressions in 1.1.1 -> 1.2 Victor Gambier
2025-02-11 10:33 ` Markus Elfring [this message]
2025-02-12 9:52 ` [cocci] Profiling of SmPL code? Markus Elfring
2026-03-27 10:43 ` [cocci] possible regressions in 1.1.1 -> 1.2 Victor Gambier
2026-03-27 10:49 ` Johannes Berg
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=e01dde43-9c07-4914-ba39-224b4eccdeb0@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=johannes@sipsolutions.net \
--cc=victor.gambier@inria.fr \
/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.