From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@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: Fri, 12 Jul 2024 21:09:26 +0200 [thread overview]
Message-ID: <20240712190926.GA399927@pevik> (raw)
In-Reply-To: <ZpE5q627g9bpxfwj@yuki>
> Hi!
> > Hm, after doing make clean of the library everything magically worked. I'm sorry
> > for the noise.
> I guess that the reason for most problems we have is that LTP does not
> have a proper dependencies in the build system. I guess that I can try
> to add support for autogenerating dep files and including them, but I'm
> afraid that with the amount of complexity we have there because of the
> out-of-tree build support things will get very complicated quite fast.
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].
But back to the reality, would it be possible to merge this even with broken
dependency? I'm not sure myself.
Kind regards,
Petr
[1] https://github.com/acerv/ltp-core/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-12 19:09 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 [this message]
2024-07-15 9:07 ` Cyril Hrubis
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=20240712190926.GA399927@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=jstultz@google.com \
--cc=ltp@lists.linux.it \
/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