From: Eric Paris <eparis@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Guy Briggs <rgb@redhat.com>,
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: Re: arm64 audit build failures in -next
Date: Sun, 24 Aug 2014 16:35:34 -0400 [thread overview]
Message-ID: <1408912534.4481.1.camel@localhost> (raw)
In-Reply-To: <20140823155043.GM24407@sirena.org.uk>
I just pushed a clean copy of Linus' tree to my audit tree. So my API
change is gone when he next pull for -next. I'm on vacation this week
and really wanted to get it fixed right before I left. It didn't
happen. when I push a new tree into next I will pick up the arm audit
patch and fix the api in my tree.
-Eric
On Sat, 2014-08-23 at 10:50 -0500, Mark Brown wrote:
> 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?
WARNING: multiple messages have this Message-ID (diff)
From: eparis@redhat.com (Eric Paris)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 audit build failures in -next
Date: Sun, 24 Aug 2014 16:35:34 -0400 [thread overview]
Message-ID: <1408912534.4481.1.camel@localhost> (raw)
In-Reply-To: <20140823155043.GM24407@sirena.org.uk>
I just pushed a clean copy of Linus' tree to my audit tree. So my API
change is gone when he next pull for -next. I'm on vacation this week
and really wanted to get it fixed right before I left. It didn't
happen. when I push a new tree into next I will pick up the arm audit
patch and fix the api in my tree.
-Eric
On Sat, 2014-08-23 at 10:50 -0500, Mark Brown wrote:
> 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?
next prev parent reply other threads:[~2014-08-24 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XLCyO-0007E5-P1@cassiel.sirena.org.uk>
2014-08-23 15:50 ` arm64 audit build failures in -next Mark Brown
2014-08-24 20:35 ` Eric Paris [this message]
2014-08-24 20:35 ` Eric Paris
2014-08-24 20:51 ` Richard Guy Briggs
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=1408912534.4481.1.camel@localhost \
--to=eparis@redhat.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.