From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
Michael William Jonathan <[email protected]>,
io-uring Mailing List <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Stefan Metzmacher <[email protected]>
Subject: [PATCH liburing v1 1/2] Makefile: Remove the `partcheck` target
Date: Tue, 19 Dec 2023 18:54:22 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Remove the `partcheck` target because it has remained unused for nearly
four years, and the associated TODO comment has not been actioned since
its introduction in commit:
b57dbc2d308a849 ("configure/Makefile: introduce libdevdir defaults to $(libdir)")
Cc: Stefan Metzmacher <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---
Makefile | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Makefile b/Makefile
index 73d021c2e46255bf..7326e644e3a18bdb 100644
--- a/Makefile
+++ b/Makefile
@@ -14,9 +14,6 @@ all:
.PHONY: all install default clean test
.PHONY: FORCE cscope
-partcheck: all
- @echo "make partcheck => TODO add tests with out kernel support"
-
runtests: all
@$(MAKE) -C test runtests
runtests-loop: all
--
Ammar Faizi
next prev parent reply other threads:[~2023-12-19 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 11:54 [PATCH liburing v1 0/2] Makefile and t/no-mmap-inval updates Ammar Faizi
2023-12-19 11:54 ` Ammar Faizi [this message]
2023-12-19 11:54 ` [PATCH liburing v1 2/2] t/no-mmap-inval: Replace `valloc()` with `t_posix_memalign()` Ammar Faizi
2023-12-19 12:05 ` Alviro Iskandar Setiawan
2023-12-19 15:22 ` [PATCH liburing v1 0/2] Makefile and t/no-mmap-inval updates Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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