From: Markus Elfring <Markus.Elfring@web.de>
To: "Martin Ågren" <martin.agren@gmail.com>, git@vger.kernel.org
Cc: Denton Liu <liu.denton@gmail.com>
Subject: Re: coccinelle: merge two rules from flex_alloc.cocci
Date: Thu, 14 Nov 2019 09:15:47 +0100 [thread overview]
Message-ID: <1d08b49e-1f41-4290-a64b-dad9fd2288de@web.de> (raw)
In-Reply-To: <CAN0heSqyGwkeGKv0m_gLDooaUp=gN2_tD7kJYNxeL7LALiPRhQ@mail.gmail.com>
> If you could have some before/after numbers, that would be cool.
Does any test infrastructure (or benchmarks) exist which you would trust for
corresponding comparisons of software run time characteristics?
> If you collect your patches into one series, you could at least do measurements
> before/after the series.
How do you think about to check possible improvements by each presented patch
according to affected SmPL scripts individually?
> Or if you could make some other sort of claim around "this shouldn't
> affect this-or-that because so-and-so".
I try to avoid such claims.
But I provided specific information in my patch descriptions.
Do you find any details reasonable there?
> Do you mean whether I would like to clarify the risks I see, or do you
> mean whether I would like you to clarify which you see?
Both. - The discussion will depend also on your change acceptance and desire
to extend development in the shown software design directions.
> I've tried to clarify the one I see -- based on passively observing cocci-related
> patches floating around this list.
Thanks for your interest.
> If you see other potential risks, feel free to mention them.
I would prefer a more optimistic view while my software development
experiences can influence this considerably.
> You seem to know lots more than I do about these things.
This can be. - But I hope that you can get further inspirations and ideas
if you would find any of the published development activities interesting enough.
Regards,
Markus
next prev parent reply other threads:[~2019-11-14 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 15:34 [PATCH] coccinelle: merge two rules from flex_alloc.cocci Markus Elfring
2019-11-12 17:59 ` Denton Liu
2019-11-13 18:27 ` Martin Ågren
2019-11-13 21:10 ` Markus Elfring
2019-11-14 6:37 ` Martin Ågren
2019-11-14 8:15 ` Markus Elfring [this message]
2019-11-14 16:35 ` SZEDER Gábor
2019-11-14 17:30 ` Markus Elfring
2019-11-15 5:13 ` Junio C Hamano
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=1d08b49e-1f41-4290-a64b-dad9fd2288de@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=martin.agren@gmail.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;
as well as URLs for NNTP newsgroup(s).