From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: John Stultz <jstultz@google.com>, ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 2/2] sched_football: Rewrite into new API
Date: Mon, 15 Jul 2024 11:07:22 +0200 [thread overview]
Message-ID: <ZpTmyoh2J1zvWHwO@yuki> (raw)
In-Reply-To: <20240712190926.GA399927@pevik>
Hi!
> I hoped there is something I just overlooked. Even I'm not a big fan of meson,
> instead of implementing something own I would consider migrating to it.
> Looking into Andrea's POV, where he did at least some work [1].
I'm afraid that meson is not good choice for us. LTP has to be able to
be compiled everywhere even on ten years old distribution and very
restricted embedded devices, hence I would like us to stay on the most
common and stable build system tooling out there. Which is plain old
make.
And the main problem with our build system is not the tooling we choose,
but the complexity imposed by the out-of-tree build implemented in the
complex makefiles. As far as I can tell 99% of the problems would be
solved by ripping out out-of-tree support, which would remove most of
the code we have in there.
> But back to the reality, would it be possible to merge this even with broken
> dependency? I'm not sure myself.
I will double check the code, before adding my final reviewed-by.
Also this is a step number one. I think that we should enable the
realtime compilation by default and the sched_football should be added
to the scheduller runtest file as well, so that it's executed by default
as well.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-15 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 10:43 [LTP] [RFC PATCH 1/2] realtime: Use offsetof() macro from <stddef.h> Petr Vorel
2024-07-11 10:43 ` [LTP] [RFC PATCH 2/2] sched_football: Rewrite into new API Petr Vorel
2024-07-12 11:21 ` Cyril Hrubis
2024-07-12 13:22 ` Petr Vorel
2024-07-12 14:11 ` Cyril Hrubis
2024-07-12 19:09 ` Petr Vorel
2024-07-15 9:07 ` Cyril Hrubis [this message]
2024-07-15 9:52 ` Petr Vorel
2024-07-15 10:38 ` Cyril Hrubis
2024-07-15 12:44 ` Petr Vorel
2024-07-17 14:52 ` Cyril Hrubis
2024-07-17 16:03 ` Petr Vorel
2024-07-12 9:57 ` [LTP] [RFC PATCH 1/2] realtime: Use offsetof() macro from <stddef.h> Cyril Hrubis
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=ZpTmyoh2J1zvWHwO@yuki \
--to=chrubis@suse.cz \
--cc=jstultz@google.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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