Netdev List
 help / color / mirror / Atom feed
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: Fri, 3 Feb 2023 18:06:15 -0700	[thread overview]
Message-ID: <975995d6-366a-88e3-2321-f0728f7e22a7@linuxfoundation.org> (raw)
In-Reply-To: <799b87d9-af19-0e6a-01b7-419b4893a0df@linuxfoundation.org>

On 2/1/23 19:07, Shuah Khan wrote:
> Hi Mathieu,
> 
> On 1/30/23 15:29, Shuah Khan wrote:
>> 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 again for taking care of this. I did out of tree build testing on
> x86 on linux-kselftest next with these patches below. I haven't seen
> any problems introduced by the patch set.
> 
>>>    selftests: dma: Fix incorrect kernel headers search path
> This one needs a change and I will send a patch on top of yours.
> Even with that this test depends on unexported header from the
> repo and won't build out of tree. This is not related to your
> change.
> 
>>>    selftests: mount_setattr: Fix incorrect kernel headers search path
> This one fails to build with our without patch - an existing error.
> 
> I have to do cross-build tests on arm64 and other arch patches still.
> This will happen later this week.

arm64, s390 patches look good.

thanks,
-- Shuah

  reply	other threads:[~2023-02-04  1:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230127135755.79929-1-mathieu.desnoyers@efficios.com>
     [not found] ` <20230127135755.79929-3-mathieu.desnoyers@efficios.com>
2023-01-30 16:12   ` [PATCH 02/34] selftests: bpf: Fix incorrect kernel headers search path Shuah Khan
2023-01-30 16:26     ` Alexei Starovoitov
2023-01-30 17:00       ` Mathieu Desnoyers
2023-01-30 17:09         ` Shuah Khan
     [not found] ` <20230127135755.79929-18-mathieu.desnoyers@efficios.com>
2023-01-30 16:24   ` [PATCH 17/34] selftests: net: " Shuah Khan
2023-01-30 22:29 ` [PATCH 00/34] selftests: " Shuah Khan
2023-01-30 23:45   ` 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 [this message]
2023-02-11  0:15       ` Shuah Khan

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=975995d6-366a-88e3-2321-f0728f7e22a7@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