From: Greg KH <gregkh@linuxfoundation.org>
To: Hardik Garg <hargar@linux.microsoft.com>
Cc: stable@vger.kernel.org, shuah@kernel.org, jeffxu@google.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
code@tyhicks.com, niyelchu@linux.microsoft.com
Subject: Re: [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown type name build failure
Date: Sun, 28 May 2023 08:42:34 +0100 [thread overview]
Message-ID: <2023052824-dagger-retread-2325@gregkh> (raw)
In-Reply-To: <20230526232136.255244-1-hargar@linux.microsoft.com>
On Fri, May 26, 2023 at 04:21:36PM -0700, Hardik Garg wrote:
> Partially backport v6.3 commit 11f75a01448f ("selftests/memfd: add
> tests for MFD_NOEXEC_SEAL MFD_EXEC") to fix an unknown type name
> build error.
> In some systems, the __u64 typedef is not present due to differences
> in system headers, causing compilation errors like this one:
>
> fuse_test.c:64:8: error: unknown type name '__u64'
> 64 | static __u64 mfd_assert_get_seals(int fd)
>
> This header includes the __u64 typedef which increases the
> likelihood of successful compilation on a wider variety of systems.
>
> Signed-off-by: Hardik Garg <hargar@linux.microsoft.com>
> ---
> tools/testing/selftests/memfd/fuse_test.c | 1 +
> 1 file changed, 1 insertion(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-05-28 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:21 [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown type name build failure Hardik Garg
2023-05-27 1:21 ` Tyler Hicks
2023-05-28 7:42 ` Greg KH [this message]
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=2023052824-dagger-retread-2325@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=code@tyhicks.com \
--cc=hargar@linux.microsoft.com \
--cc=jeffxu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=niyelchu@linux.microsoft.com \
--cc=shuah@kernel.org \
--cc=stable@vger.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