All of lore.kernel.org
 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] include/lapi: add leaf Makefile
Date: Thu, 16 Apr 2026 20:11:29 +0200	[thread overview]
Message-ID: <20260416181129.GB303991@pevik> (raw)
In-Reply-To: <20260416144626.6037-1-always.starving0@gmail.com>

Hi Jinseok,

> Hi,

> Thanks for the review!
Yw.

> If we switch to generic_trunk, the current directory is not checked;
> only subdirectories are traversed.

FYI by this I meant this change (part of more changes stated previously):

diff --git include/Makefile include/Makefile
index 6b31b046e4..84cd4ed6e3 100644
--- include/Makefile
+++ 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

> For example, running `make check` in include/ will descend into
> include/lapi, and running `make check` in include/lapi will descend
> into include/lapi/syscalls.

And with that change make check in include works:

ltp/include $ make check-tst_fs.h
CHECK include/tst_fs.h
tst_fs.h:83: CHECK: 'swtich' may be misspelled - perhaps 'switch'?
tst_fs.h:157: WARNING: please, no spaces at the start of a line
tst_fs.h:157: WARNING: Prefer __printf(1, 2) over __attribute__((format(printf, 1, 2)))
make: [../include/mk/rules.mk:69: check-tst_fs.h] Error 1 (ignored)

ltp/include/lapi $ make check-tls.h
CHECK include/lapi/tls.h
tls.h:1: WARNING: Improper SPDX comment style for 'tls.h', please use '/*' instead
tls.h:1: WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
tls.h:35: WARNING: do not add new typedefs
tls.h:49: WARNING: Missing a blank line after declarations
tls.h:56: WARNING: Missing a blank line after declarations
make: [../../include/mk/rules.mk:69: check-tls.h] Error 1 (ignored)

Kind regards,
Petr

> Thanks,
> Jinseok.

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

  reply	other threads:[~2026-04-16 18:12 UTC|newest]

Thread overview: 14+ 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 [this message]
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             ` [LTP] [PATCH v2] " 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=20260416181129.GB303991@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.