From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Bernd Kuhls <bernd@kuhls.net>
Subject: [PATCH i-g-t v1 2/3] lib/igt_kmod: fix musl builds
Date: Fri, 15 Mar 2024 14:19:00 +0100 [thread overview]
Message-ID: <20240315131901.28144-3-kamil.konieczny@linux.intel.com> (raw)
In-Reply-To: <20240315131901.28144-1-kamil.konieczny@linux.intel.com>
On musl build the PATH_MAX define is missing, fixed this with
including limits.h
Link: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/138
Cc: Bernd Kuhls <bernd@kuhls.net>
Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
lib/igt_kmod.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
index b4b884898..0b01f070f 100644
--- a/lib/igt_kmod.c
+++ b/lib/igt_kmod.c
@@ -25,6 +25,7 @@
#include <dirent.h>
#include <errno.h>
#include <fcntl.h>
+#include <limits.h>
#include <pthread.h>
#include <signal.h>
#include <stdlib.h>
--
2.42.0
next prev parent reply other threads:[~2024-03-15 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 13:18 [PATCH i-g-t v1 0/3] more musl libc fixes for PATH_MAX Kamil Konieczny
2024-03-15 13:18 ` [PATCH i-g-t v1 1/3] lib/igt_sriov_device: fix musl libc build Kamil Konieczny
2024-03-18 10:59 ` Juha-Pekka Heikkila
2024-03-18 13:38 ` Mauro Carvalho Chehab
2024-03-15 13:19 ` Kamil Konieczny [this message]
2024-03-18 13:38 ` [PATCH i-g-t v1 2/3] lib/igt_kmod: fix musl builds Mauro Carvalho Chehab
2024-03-15 13:19 ` [PATCH i-g-t v1 3/3] tests/intel/xe_debugfs: fix musl build Kamil Konieczny
2024-03-18 13:39 ` Mauro Carvalho Chehab
2024-03-15 14:59 ` ✓ Fi.CI.BAT: success for more musl libc fixes for PATH_MAX Patchwork
2024-03-15 15:06 ` ✓ CI.xeBAT: " Patchwork
2024-03-16 17:46 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-18 11:24 ` Kamil Konieczny
2024-03-21 4:30 ` Illipilli, TejasreeX
2024-03-20 17:24 ` ✓ Fi.CI.IGT: success " Patchwork
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=20240315131901.28144-3-kamil.konieczny@linux.intel.com \
--to=kamil.konieczny@linux.intel.com \
--cc=bernd@kuhls.net \
--cc=igt-dev@lists.freedesktop.org \
/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.