mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Guillaume Tucker" <guillaume.tucker@collabora.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock fix for v6.0 #2
Date: Fri, 23 Sep 2022 12:43:22 +0200	[thread overview]
Message-ID: <20220923104322.3182116-1-mic@digikod.net> (raw)

Hi Linus,

This change fixes out-of-tree builds for Landlock tests, which was
initially identified here:
https://lore.kernel.org/r/CADYN=9JM1nnjC9LypHqrz7JJjbZLpm8rArDUy4zgYYrajErBnA@mail.gmail.com

Please pull this Landlock fix for v6.0-rc7 .  This change merged
cleanly with your tree, and have been successfully tested in the latest
linux-next releases for a week.

Regards,
 Mickaël

--
The following changes since commit 80e78fcce86de0288793a0ef0f6acf37656ee4cf:

  Linux 6.0-rc5 (2022-09-11 16:22:01 -0400)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.0-rc7

for you to fetch changes up to a52540522c9541bfa3e499d2edba7bc0ca73a4ca:

  selftests/landlock: Fix out-of-tree builds (2022-09-14 16:37:38 +0200)

----------------------------------------------------------------
Landlock fix for v6.0-rc7

----------------------------------------------------------------
Mickaël Salaün (1):
      selftests/landlock: Fix out-of-tree builds

 tools/testing/selftests/landlock/Makefile | 19 ++++++++++---------
 tools/testing/selftests/lib.mk            |  4 ++++
 2 files changed, 14 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-09-23 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 10:43 Mickaël Salaün [this message]
2022-09-23 14:42 ` Shuah Khan
2022-09-23 16:25 ` pr-tracker-bot

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=20220923104322.3182116-1-mic@digikod.net \
    --to=mic@digikod.net \
    --cc=anders.roxell@linaro.org \
    --cc=broonie@kernel.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®