From: Randy Dunlap <rdunlap@infradead.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Peter Xu <peterx@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [next] s390: build failed
Date: Thu, 21 Apr 2022 08:32:24 -0700 [thread overview]
Message-ID: <d7b81bef-5f51-2b42-6f84-ec09d9b469ff@infradead.org> (raw)
In-Reply-To: <CA+G9fYvA9e760hFH==n2_gn8zNQeGBQ1=8_+Ot1sMCwoPiS15g@mail.gmail.com>
On 4/21/22 02:57, Naresh Kamboju wrote:
> Linux next-20220421 s390 tinyconfig and allnoconfig builds failed [1].
>
> Regressions found on s390:
> - s390-clang-nightly-tinyconfig
> - s390-gcc-10-tinyconfig
> - s390-gcc-11-tinyconfig
> - s390-clang-14-allnoconfig
> - s390-clang-nightly-allnoconfig
> - s390-clang-14-tinyconfig
> - s390-clang-13-tinyconfig
> - s390-gcc-10-allnoconfig
> - s390-clang-13-allnoconfig
> - s390-gcc-9-allnoconfig
> - s390-gcc-9-tinyconfig
> - s390-gcc-11-allnoconfig
> - s390-gcc-8-tinyconfig
> - s390-gcc-8-allnoconfig
>
> In file included from arch/s390/mm/pageattr.c:6:
> include/linux/hugetlb.h:414:25: error: unknown type name
> 'zap_flags_t'; did you mean 'vm_flags_t'?
> 414 | zap_flags_t zap_flags)
> | ^~~~~~~~~~~
> | vm_flags_t
> make[3]: *** [scripts/Makefile.build:284: arch/s390/mm/pageattr.o] Error 1
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
Here's a fix:
https://lore.kernel.org/lkml/20220421014723.5802-1-rdunlap@infradead.org/
> --
> Linaro LKFT
> https://lkft.linaro.org
>
> [1] https://builds.tuxbuild.com/2868Z0YrLSpSGSk9QDqRKYMJPug/
--
~Randy
prev parent reply other threads:[~2022-04-21 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 9:57 Naresh Kamboju
2022-04-21 15:32 ` Randy Dunlap [this message]
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=d7b81bef-5f51-2b42-6f84-ec09d9b469ff@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterx@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox