From: Shuah Khan <skhan@linuxfoundation.org>
To: "Guillaume Tucker" <guillaume.tucker@collabora.com>,
Guillaume <guillaume.tucker@gmail.com>,
"Shuah Khan" <shuah@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>
Cc: Anders Roxell <anders.roxell@linaro.org>,
Tim.Bird@sony.com, kernel@collabora.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-security-module@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/landlock: fix broken include of linux/landlock.h
Date: Wed, 3 Aug 2022 17:08:12 -0600 [thread overview]
Message-ID: <677a5a8f-87df-dde6-0adc-292858e4b5bd@linuxfoundation.org> (raw)
In-Reply-To: <a459363217b1847c0f206a5dbdf181cb21cf3d0c.1659557290.git.guillaume.tucker@collabora.com>
On 8/3/22 2:13 PM, Guillaume Tucker wrote:
> Revert part of the earlier changes to fix the kselftest build when
> using a sub-directory from the top of the tree as this broke the
> landlock test build as a side-effect when building with "make -C
> tools/testing/selftests/landlock".
>
> Reported-by: Mickaël Salaün <mic@digikod.net>
> Fixes: a917dd94b832 ("selftests/landlock: drop deprecated headers dependency")
> Fixes: f2745dc0ba3d ("selftests: stop using KSFT_KHDR_INSTALL")
> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> ---
> tools/testing/selftests/landlock/Makefile | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Thank you. Now applied to linux-kselftest next for the next pull request.
thanks,
-- Shuah
next prev parent reply other threads:[~2022-08-03 23:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 20:13 [PATCH] selftests/landlock: fix broken include of linux/landlock.h Guillaume Tucker
2022-08-03 23:08 ` Shuah Khan [this message]
2022-08-04 10:36 ` Mickaël Salaün
2022-08-04 19:38 ` Guillaume Tucker
2022-08-05 17:16 ` Mickaël Salaün
2022-08-12 15:29 ` Mickaël Salaün
2022-08-15 17:17 ` Shuah Khan
2022-08-16 16:57 ` Mickaël Salaün
2022-08-13 10:01 ` Anders Roxell
2022-08-13 12:31 ` Mickaël Salaün
2022-08-22 14:00 ` Anders Roxell
2022-08-25 9:31 ` Mickaël Salaün
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=677a5a8f-87df-dde6-0adc-292858e4b5bd@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=anders.roxell@linaro.org \
--cc=guillaume.tucker@collabora.com \
--cc=guillaume.tucker@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--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;
as well as URLs for NNTP newsgroup(s).