From: Jinseok Kim <always.starving0@gmail.com>
To: wangli.ahau@gmail.com, pvorel@suse.cz
Cc: ltp@lists.linux.it
Subject: [LTP] [PATCH] include/lapi: add leaf Makefile
Date: Thu, 16 Apr 2026 23:46:21 +0900 [thread overview]
Message-ID: <20260416144626.6037-1-always.starving0@gmail.com> (raw)
In-Reply-To: <CANgNiRztOnor2mgLyfGxiCE01qyBwcsnZcrv1ZUi14KeFzctQw@mail.gmail.com>
Hi,
Thanks for the review!
If we switch to generic_trunk, the current directory is not checked;
only subdirectories are traversed.
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.
Thanks,
Jinseok.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-16 14:47 UTC|newest]
Thread overview: 11+ 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 [this message]
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
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=20260416144626.6037-1-always.starving0@gmail.com \
--to=always.starving0@gmail.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=wangli.ahau@gmail.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