From: Mark Brown <broonie@kernel.org>
To: Eric Paris <eparis@redhat.com>, Richard Guy Briggs <rgb@redhat.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linaro-kernel@lists.linaro.org,
linux-arm-kernel@lists.infradead.org, linux-audit@redhat.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
kernel-build-reports@lists.linaro.org
Subject: arm64 audit build failures in -next
Date: Sat, 23 Aug 2014 10:50:43 -0500 [thread overview]
Message-ID: <20140823155043.GM24407@sirena.org.uk> (raw)
In-Reply-To: <E1XLCyO-0007E5-P1@cassiel.sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Sat, Aug 23, 2014 at 04:11:20PM +0100, Build bot for Mark Brown wrote:
> arm64-allmodconfig
> ../arch/arm64/kernel/ptrace.c:1120:3: error: too many arguments to function 'audit_syscall_entry'
This has now been broken in -next for about a month with a fix available
and since the merge window the arm64 audit support is in mainline so the
fix can be directly applied without cross tree issues (the audit changes
didn't get sent during the merge window). Catalin and Will have also
indicated that they want to remove the workaround that's in -next
currently to allow defconfig to build which would make the situation
even more pressing.
Do we have any idea when it will be possible to get a fix into -next?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2014-08-23 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XLCyO-0007E5-P1@cassiel.sirena.org.uk>
2014-08-23 15:50 ` Mark Brown [this message]
2014-08-24 20:35 ` arm64 audit build failures in -next Eric Paris
2014-08-24 20:51 ` Richard Guy Briggs
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=20140823155043.GM24407@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=eparis@redhat.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=will.deacon@arm.com \
/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