Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: "Ricardo B . Marlière" <rbm@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 1/2] Makefile: Add kernel modules related make targets
Date: Thu, 7 Aug 2025 07:11:33 +0200	[thread overview]
Message-ID: <20250807051133.GA331644@pevik> (raw)
In-Reply-To: <CAEemH2ddKZwocZbpf9vUVjNssbonifJG5o7hu-PoBggZocXVSA@mail.gmail.com>

Hi Li, all,

> On Thu, Aug 7, 2025 at 7:22 AM Li Wang <liwang@redhat.com> wrote:

> > Hi Petr,

> > On Thu, Aug 7, 2025 at 5:14 AM Petr Vorel <pvorel@suse.cz> wrote:

> >> LTP contains few kernel modules and tests which are using them.  These
> >> require to be built with the same kernel headers as the running kernel
> >> (SUT). Sometimes the best way to achieve this is to compile them on the
> >> SUT.

> >> Add 'modules', 'modules-clean' and 'modules-install' make targets to
> >> make it easier to build them.


> > Maybe better to keep the make target consistent with the kernel build
> > command:
> >   make modules_install
> >   make modules_clean

> Also, it looks like LTP mixes using "-" and "_" in its make targets:

>   lib-all, metadata-all, clean_install_dir, ver_linux

I chose '-' because that's what uses LTP for make targets.
ver_linux uses underscore because target inherits it from the name of the file.

clean_install_dir is the only target which uses '_', I'm not sure why this
inconsistency.

> So we may need to use just one selection, which can be done in a separate
> patch anyway.

I got the point that kernel uses '_'. Do we want to unify after years using '-'?
I'm ok to do the work if we consider it's useful.

I personally consider more important from the long term to change build system
to meson (de facto standard for the userspace projects, including these related
to kernel).

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-08-07  5:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 21:14 [LTP] [PATCH v3 1/2] Makefile: Add kernel modules related make targets Petr Vorel
2025-08-06 21:14 ` [LTP] [PATCH v3 2/2] modules.mk: Add FORCE_MODULES=1 to fail on error Petr Vorel
2025-08-07  3:37   ` Li Wang via ltp
2025-08-07  6:17     ` Petr Vorel
2025-08-06 23:22 ` [LTP] [PATCH v3 1/2] Makefile: Add kernel modules related make targets Li Wang via ltp
2025-08-07  2:15   ` Li Wang via ltp
2025-08-07  5:11     ` Petr Vorel [this message]
2025-08-07  7:56       ` Li Wang via ltp

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=20250807051133.GA331644@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=rbm@suse.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