From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dominik Brodowski <linux@dominikbrodowski•net>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: build failure after merge of the syscalls tree
Date: Wed, 14 Mar 2018 15:57:25 +1100 [thread overview]
Message-ID: <20180314155725.581ee5ca@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi Dominik,
After merging the syscalls tree, today's linux-next build (x86_64
allnoconfig) failed like this:
Caused by commit
3e334170db85 ("mm: use do_futex() instead of sys_futex() in mm_release()")
CONFIG_FUTEX is not set for this build. Normally sys_futex() would be
the one from kernel/sys_ni.c in this case ...
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-03-14 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 4:57 Stephen Rothwell [this message]
2018-03-14 4:59 ` linux-next: build failure after merge of the syscalls tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2018-03-14 5:12 Stephen Rothwell
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=20180314155725.581ee5ca@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@dominikbrodowski$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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