From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] doc: Correct the reference to kernel documentation
Date: Tue, 3 Oct 2023 12:22:37 +0530 [thread overview]
Message-ID: <20231003065238.31896-1-akumar@suse.de> (raw)
Signed-off-by: Avinesh Kumar <akumar@suse.de>
---
doc/build-system-guide.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/build-system-guide.txt b/doc/build-system-guide.txt
index e078fa7f7..95ba3b70e 100644
--- a/doc/build-system-guide.txt
+++ b/doc/build-system-guide.txt
@@ -112,7 +112,7 @@ the module because the file does not exists, the test is skipped.
Note the 'ifneq($(KERNELRELEASE),)', the reason it's there is that the
Makefile is executed twice, once by LTP build system and once by kernel
-kbuild, see 'Documentation/kbuild/modules.txt' in the Linux kernel tree for
+kbuild, see 'Documentation/kbuild/modules.rst' in the Linux kernel tree for
details on external module build.
Make Rules and Make Variables
--
2.42.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2023-10-03 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 6:52 Avinesh Kumar [this message]
2023-10-04 14:01 ` [LTP] [PATCH] doc: Correct the reference to kernel documentation 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=20231003065238.31896-1-akumar@suse.de \
--to=akumar@suse.de \
--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