From: Shuah Khan <skhan@linuxfoundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org, bpf <bpf@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 00/34] selftests: Fix incorrect kernel headers search path
Date: Mon, 30 Jan 2023 15:29:21 -0700 [thread overview]
Message-ID: <560824bd-da2d-044c-4f71-578fc34a47cd@linuxfoundation.org> (raw)
In-Reply-To: <20230127135755.79929-1-mathieu.desnoyers@efficios.com>
On 1/27/23 06:57, Mathieu Desnoyers wrote:
> Hi,
>
> This series fixes incorrect kernel header search path in kernel
> selftests.
>
> Near the end of the series, a few changes are not tagged as "Fixes"
> because the current behavior is to rely on the kernel sources uapi files
> rather than on the installed kernel header files. Nevertheless, those
> are updated for consistency.
>
> There are situations where "../../../../include/" was added to -I search
> path, which is bogus for userspace tests and caused issues with types.h.
> Those are removed.
>
> Thanks,
>
> Mathieu
>
> Mathieu Desnoyers (34):
The below patches are now applied to linux-kselftest next for Linux 6.3-rc1
> selftests: arm64: Fix incorrect kernel headers search path
> selftests: clone3: Fix incorrect kernel headers search path
> selftests: core: Fix incorrect kernel headers search path
> selftests: dma: Fix incorrect kernel headers search path
> selftests: dmabuf-heaps: Fix incorrect kernel headers search path
> selftests: drivers: Fix incorrect kernel headers search path
> selftests: filesystems: Fix incorrect kernel headers search path
> selftests: futex: Fix incorrect kernel headers search path
> selftests: gpio: Fix incorrect kernel headers search path
> selftests: ipc: Fix incorrect kernel headers search path
> selftests: kcmp: Fix incorrect kernel headers search path
> selftests: media_tests: Fix incorrect kernel headers search path
> selftests: membarrier: Fix incorrect kernel headers search path
> selftests: mount_setattr: Fix incorrect kernel headers search path
> selftests: move_mount_set_group: Fix incorrect kernel headers search
> path
> selftests: perf_events: Fix incorrect kernel headers search path
> selftests: pid_namespace: Fix incorrect kernel headers search path
> selftests: pidfd: Fix incorrect kernel headers search path
> selftests: ptp: Fix incorrect kernel headers search path
> selftests: rseq: Fix incorrect kernel headers search path
> selftests: sched: Fix incorrect kernel headers search path
> selftests: seccomp: Fix incorrect kernel headers search path
> selftests: sync: Fix incorrect kernel headers search path
> selftests: user_events: Fix incorrect kernel headers search path
> selftests: vm: Fix incorrect kernel headers search path
> selftests: x86: Fix incorrect kernel headers search path
> selftests: iommu: Use installed kernel headers search path
> selftests: memfd: Use installed kernel headers search path
> selftests: ptrace: Use installed kernel headers search path
> selftests: tdx: Use installed kernel headers search path
>
These will be applied by maintainers to their trees.
> selftests: bpf: Fix incorrect kernel headers search path # 02/34
> selftests: net: Fix incorrect kernel headers search path # 17/34
> selftests: powerpc: Fix incorrect kernel headers search path # 21/34
> selftests: bpf docs: Use installed kernel headers search path # 30/34
thanks,
-- Shuah
next prev parent reply other threads:[~2023-01-30 22:29 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:57 [PATCH 00/34] selftests: Fix incorrect kernel headers search path Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 01/34] selftests: arm64: " Mathieu Desnoyers
2023-01-30 16:09 ` Shuah Khan
2023-01-30 17:14 ` Catalin Marinas
2023-01-30 17:20 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 02/34] selftests: bpf: " Mathieu Desnoyers
2023-01-30 16:12 ` Shuah Khan
2023-01-30 16:26 ` Alexei Starovoitov
2023-01-30 17:00 ` Mathieu Desnoyers
2023-01-30 17:09 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 03/34] selftests: clone3: " Mathieu Desnoyers
2023-01-30 16:15 ` Shuah Khan
2023-01-30 16:26 ` Christian Brauner
2023-01-27 13:57 ` [PATCH 04/34] selftests: core: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 05/34] selftests: dma: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 06/34] selftests: dmabuf-heaps: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 07/34] selftests: drivers: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 08/34] selftests: filesystems: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 09/34] selftests: futex: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 10/34] selftests: gpio: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 11/34] selftests: ipc: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 12/34] selftests: kcmp: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 13/34] selftests: media_tests: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 14/34] selftests: membarrier: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 15/34] selftests: mount_setattr: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 16/34] selftests: move_mount_set_group: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 17/34] selftests: net: " Mathieu Desnoyers
2023-01-27 16:21 ` Matthieu Baerts
2023-01-27 16:42 ` Mathieu Desnoyers
2023-01-30 16:24 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 18/34] selftests: perf_events: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 19/34] selftests: pid_namespace: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 20/34] selftests: pidfd: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 21/34] selftests: powerpc: " Mathieu Desnoyers
2023-01-30 16:32 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 22/34] selftests: ptp: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 23/34] selftests: rseq: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 24/34] selftests: sched: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 25/34] selftests: seccomp: " Mathieu Desnoyers
2023-01-30 16:52 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 26/34] selftests: sync: " Mathieu Desnoyers
2023-01-30 16:44 ` Shuah Khan
2023-01-30 16:51 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 27/34] selftests: user_events: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 28/34] selftests: vm: " Mathieu Desnoyers
2023-01-30 16:55 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 29/34] selftests: x86: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 30/34] selftests: bpf docs: Use installed " Mathieu Desnoyers
2023-01-30 16:57 ` Shuah Khan
2023-01-27 13:57 ` [PATCH 31/34] selftests: iommu: " Mathieu Desnoyers
2023-01-30 17:01 ` Shuah Khan
2023-01-30 17:05 ` Jason Gunthorpe
2023-01-27 13:57 ` [PATCH 32/34] selftests: memfd: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 33/34] selftests: ptrace: " Mathieu Desnoyers
2023-01-27 13:57 ` [PATCH 34/34] selftests: tdx: " Mathieu Desnoyers
2023-01-30 22:29 ` Shuah Khan [this message]
2023-01-30 23:45 ` [PATCH 00/34] selftests: Fix incorrect " Alexei Starovoitov
2023-01-30 23:48 ` Shuah Khan
2023-01-30 23:49 ` Alexei Starovoitov
2023-02-02 2:07 ` Shuah Khan
2023-02-04 1:06 ` Shuah Khan
2023-02-11 0:15 ` Shuah Khan
2023-02-20 3:49 ` (subset) " Michael Ellerman
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=560824bd-da2d-044c-4f71-578fc34a47cd@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox