From: Kees Cook <keescook@chromium.org>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linux-mm@kvack.org, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [powerpc] Build failure include/linux/compiler_types.h __alloc_size__ (next-20220928)
Date: Thu, 29 Sep 2022 01:17:37 -0700 [thread overview]
Message-ID: <202209290116.AF9A13DF@keescook> (raw)
In-Reply-To: <E3F43AE3-E1AA-4992-9308-C0E790478445@linux.ibm.com>
On Thu, Sep 29, 2022 at 11:49:28AM +0530, Sachin Sant wrote:
> Linux-next 6.0.0-rc7-next-20220928 fails to build on powerpc with
> following error:
>
> make -j 17 -s && make modules_install && make install
> In file included from <command-line>:
> ./include/linux/percpu.h: In function '__alloc_reserved_percpu':
> ././include/linux/compiler_types.h:279:30: error: expected declaration specifiers before '__alloc_size__'
> #define __alloc_size(x, ...) __alloc_size__(x, ## __VA_ARGS__) __malloc
> ^~~~~~~~~~~~~~
Apologies for the breakage! This should be fixed by:
https://lore.kernel.org/lkml/20220929081642.1932200-1-keescook@chromium.org
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Sachin Sant <sachinp@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [powerpc] Build failure include/linux/compiler_types.h __alloc_size__ (next-20220928)
Date: Thu, 29 Sep 2022 01:17:37 -0700 [thread overview]
Message-ID: <202209290116.AF9A13DF@keescook> (raw)
In-Reply-To: <E3F43AE3-E1AA-4992-9308-C0E790478445@linux.ibm.com>
On Thu, Sep 29, 2022 at 11:49:28AM +0530, Sachin Sant wrote:
> Linux-next 6.0.0-rc7-next-20220928 fails to build on powerpc with
> following error:
>
> make -j 17 -s && make modules_install && make install
> In file included from <command-line>:
> ./include/linux/percpu.h: In function '__alloc_reserved_percpu':
> ././include/linux/compiler_types.h:279:30: error: expected declaration specifiers before '__alloc_size__'
> #define __alloc_size(x, ...) __alloc_size__(x, ## __VA_ARGS__) __malloc
> ^~~~~~~~~~~~~~
Apologies for the breakage! This should be fixed by:
https://lore.kernel.org/lkml/20220929081642.1932200-1-keescook@chromium.org
--
Kees Cook
next prev parent reply other threads:[~2022-09-29 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 6:19 [powerpc] Build failure include/linux/compiler_types.h __alloc_size__ (next-20220928) Sachin Sant
2022-09-29 8:17 ` Kees Cook [this message]
2022-09-29 8:17 ` Kees Cook
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=202209290116.AF9A13DF@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sachinp@linux.ibm.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.