public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jinseok Kim <always.starving0@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] include/lapi: add leaf Makefile
Date: Wed, 22 Apr 2026 07:18:00 +0200	[thread overview]
Message-ID: <20260422051800.GA392764@pevik> (raw)
In-Reply-To: <20260421160828.4483-1-always.starving0@gmail.com>

Hi Jinseok,

> Convert include/Makefile to use generic_trunk_target.mk and
> add minimal leaf Makefile in include/lapi.

add minimal leaf Makefile in include/lapi in order to have 'make check'.

FYI AI is correct it's better to describe the reason (although we have a ticket,
one day might github disappear and we lost the reason in the ticket).

Reviewed-by: Petr Vorel <pvorel@suse.cz>
Wait little longer if Li has time to ack this.

> Fixes: https://github.com/linux-test-project/ltp/issues/1262

> Signed-off-by: Jinseok Kim <always.starving0@gmail.com>
> ---
> Changes in v2:
> - Switch include/Makefile to trunk and remove lapi/syscalls/Makefile
> - Link to v1 : https://lore.kernel.org/ltp/20260410175031.16921-1-always.starving0@gmail.com
> ---
>  include/Makefile      |  2 +-
>  include/lapi/Makefile | 10 ++++++++++
>  2 files changed, 11 insertions(+), 1 deletion(-)
>  create mode 100644 include/lapi/Makefile

> diff --git a/include/Makefile b/include/Makefile
> index 6b31b046e..84cd4ed6e 100644
> --- a/include/Makefile
> +++ b/include/Makefile
> @@ -24,4 +24,4 @@ ac-maintainer-clean:: ac-clean

>  vpath %.h $(abs_srcdir)

> -include $(top_srcdir)/include/mk/generic_leaf_target.mk
> +include $(top_srcdir)/include/mk/generic_trunk_target.mk
> diff --git a/include/lapi/Makefile b/include/lapi/Makefile
> new file mode 100644
> index 000000000..f265f856d
> --- /dev/null
> +++ b/include/lapi/Makefile
> @@ -0,0 +1,10 @@
> +# SPDX-License-Identifier: GPL-2.0-or-later
> +# Copyright (C) 2009, Cisco Systems Inc.
I'll remove this line before merge. IMHO it's no longer Cisco work :).
While this is related when code is significantly based on old code,
I would not bother with 2 lines of Makefile.

> +# Copyright (c) Linux Test Project, 2026
> +# Ngie Cooper, July 2009
And this one.

Kind regards,
Petr

> +
> +top_srcdir              ?= ../../
> +
> +include $(top_srcdir)/include/mk/env_pre.mk
> +
> +include $(top_srcdir)/include/mk/generic_leaf_target.mk

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

  parent reply	other threads:[~2026-04-22  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 17:50 [LTP] [PATCH] include/lapi: add leaf Makefile Jinseok Kim
2026-04-13  9:04 ` Li Wang
2026-04-13 21:20 ` Petr Vorel
2026-04-14  7:55   ` Li Wang
2026-04-16 14:46     ` Jinseok Kim
2026-04-16 18:11       ` Petr Vorel
2026-04-16 18:05     ` Petr Vorel
2026-04-16 23:24       ` Li Wang
2026-04-17  0:11         ` Li Wang
2026-04-17 11:41           ` Petr Vorel
2026-04-17 11:34         ` Petr Vorel
2026-04-21 16:08           ` [LTP] [PATCH v2] " Jinseok Kim
2026-04-21 17:05             ` [LTP] " linuxtestproject.agent
2026-04-22  5:18             ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-22  5:26 [LTP] [PATCH v2] " Li Wang
2026-04-22 11:34 ` Petr Vorel

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=20260422051800.GA392764@pevik \
    --to=pvorel@suse.cz \
    --cc=always.starving0@gmail.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