From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@gmail.com>
Cc: Andrei Vagin <avagin@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: linux-next: build failure after merge of the seccomp tree
Date: Wed, 28 Jun 2023 22:58:52 -0700 [thread overview]
Message-ID: <202306282258.219B185B@keescook> (raw)
In-Reply-To: <CANaxB-z0gLxOU-EVnag=pi3cC164stbOVOMmaGMwNs_g43z9_w@mail.gmail.com>
On Wed, Jun 28, 2023 at 10:27:09PM -0700, Andrei Vagin wrote:
> Probably something went wrong when the patch was applied. I've checked
> that the patch contains this file:
>
> https://patchew.org/linux/20230308073201.3102738-1-avagin@google.com/20230308073201.3102738-7-avagin@google.com/
>
> Kees, could you take a look at this?
Hmm, it seems something else went wrong too, due to:
616b14b47a86 ("perf build: Conditionally define NDEBUG")
I've added "#undef NDEBUG" to the file too.
--
Kees Cook
next prev parent reply other threads:[~2023-06-29 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 2:40 linux-next: build failure after merge of the seccomp tree Stephen Rothwell
2023-06-29 5:27 ` Andrei Vagin
2023-06-29 5:30 ` Kees Cook
2023-06-29 5:58 ` Kees Cook [this message]
2023-06-30 5:22 ` Andrei Vagin
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=202306282258.219B185B@keescook \
--to=keescook@chromium.org \
--cc=avagin@gmail.com \
--cc=avagin@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.