From: Mark Brown <broonie@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: test failure after merge of the landlock tree
Date: Tue, 20 Oct 2026 10:54:29 +0100 [thread overview]
Message-ID: <atc6Vczti_EjFrQq@sirena.co.uk> (raw)
In-Reply-To: <20261019.Za1phooV2oom@digikod.net>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Mon, Oct 19, 2026 at 11:11:20PM +0200, Mickaël Salaün wrote:
> On Mon, Oct 19, 2026 at 07:17:09PM +0100, Mark Brown wrote:
> > This issue is still present today.
> I removed these wrong kunit checks Friday so it should be good now, but
> I notice that linux-next still has the next-20261001/landlock merge
> commit instead of the latest changes from mic/next (which should not
> conflict). Could you please confirm that a normal merge works?
It was broken with whatever I fetched yesterday hence me reporting it
still broken and merging the old version, I've just started the merge
for today so I'll find out this afternoon if the fix worked.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-20 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 0:31 Mark Brown
2026-10-19 18:17 ` Mark Brown
2026-10-19 21:11 ` Mickaël Salaün
2026-10-20 9:54 ` Mark Brown [this message]
2026-10-20 12:28 ` Mickaël Salaün
2026-10-20 13:02 ` Mark Brown
2026-10-20 13:16 ` Mickaël Salaün
2026-10-20 13:33 ` Mark Brown
2026-10-20 13:47 ` Mickaël Salaün
2026-10-20 13:46 ` Mark Brown
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=atc6Vczti_EjFrQq@sirena.co.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mic@digikod.net \
/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®