From: Mark Brown <broonie@kernel.org>
To: Zi Yan <ziy@nvidia.com>
Cc: wang lian <lianux.mm@gmail.com>,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
david@redhat.com, sj@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, Liam.Howlett@oracle.com, brauner@kernel.org,
gkwang@linx-info.com, jannh@google.com, p1ucky0923@gmail.com,
ryncsn@gmail.com, vbabka@suse.cz, zijing.zhang@proton.me
Subject: Re: [PATCH v4] selftests/mm: add process_madvise() tests
Date: Fri, 11 Jul 2025 09:05:33 +0100 [thread overview]
Message-ID: <aHDFzeSJlh8caDQX@finisterre.sirena.org.uk> (raw)
In-Reply-To: <1C943CB7-D63C-41F9-B676-90261E26F049@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Thu, Jul 10, 2025 at 12:21:36PM -0400, Zi Yan wrote:
> On 10 Jul 2025, at 9:42, Mark Brown wrote:
> > On Thu, Jul 10, 2025 at 07:22:49PM +0800, wang lian wrote:
> >> +#include <linux/pidfd.h>
> >> +#include <linux/uio.h>
> > Does this work without 'make headers_install' for the systems that were
> > affectd by missing headers? Lorenzo mentioned that we shouldn't depend
> > on that for the mm tests (I'm not enthusiastic about that approach
> > myself, but if it's what mm needs).
> No. “make headers_install” is still needed. I tried to get it compiled
> without it but failed. It seems that a lot of files will need to be
> copied to tools/include from “make headers”.
If you're doing that it should again be a separate patch. Another
option if it's just a few defines or something is to copy just them into
your program.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-11 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 11:22 wang lian
2025-07-10 13:42 ` Mark Brown
2025-07-10 16:21 ` Zi Yan
2025-07-11 8:05 ` Mark Brown [this message]
2025-07-11 12:19 ` [PATCH v3] " wang lian
2025-07-10 16:57 ` [PATCH v4] " Lorenzo Stoakes
2025-07-11 8:11 ` Mark Brown
2025-07-11 8:53 ` Lorenzo Stoakes
2025-07-11 9:29 ` Mark Brown
2025-07-11 11:16 ` wang lian
2025-07-11 11:33 ` Lorenzo Stoakes
2025-07-11 12:02 ` wang lian
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=aHDFzeSJlh8caDQX@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=gkwang@linx-info.com \
--cc=jannh@google.com \
--cc=lianux.mm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=p1ucky0923@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=zijing.zhang@proton.me \
--cc=ziy@nvidia.com \
/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