From: Nathan Chancellor <nathan@kernel.org>
To: Ryutaroh Matsumoto <ryutaroh@ict.e.titech.ac.jp>
Cc: masahiroy@kernel.org, yangtiezhu@loongson.cn,
tsbogend@alpha.franken.de, jason@bluehome.net,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: Makefile: Remove "ifdef need-compiler" for Kbuild.platforms
Date: Sun, 12 Dec 2021 19:09:14 -0700 [thread overview]
Message-ID: <YbarSpe7zhTi+2h4@archlinux-ax161> (raw)
In-Reply-To: <20211213.093520.538389512409174784.ryutaroh@ict.e.titech.ac.jp>
On Mon, Dec 13, 2021 at 09:35:20AM +0900, Ryutaroh Matsumoto wrote:
> From: Masahiro Yamada <masahiroy@kernel.org>
> Subject: Re: [PATCH v2] MIPS: Makefile: Remove "ifdef need-compiler" for Kbuild.platforms
> Date: Sat, 11 Dec 2021 01:39:10 +0900
> > Nathan's patch cleaned up arch/mips/loognson2ef/Platform,
> > but I still see similar code in arch/mips/sgi-ip22/Platform.
> >
> >
> > ifdef CONFIG_SGI_IP28
> > ifeq ($(call cc-option-yn,-march=r10000 -mr10k-cache-barrier=store), n)
> > $(error gcc doesn't support needed option -mr10k-cache-barrier=store)
> > endif
> > endif
> >
> >
> > Doesn't this cause a failure of *-pkg builds for sgi-ip22 platform?
>
> Yes, it does, as reported at
> https://github.com/ClangBuiltLinux/linux/issues/1543
It seems like that section can be removed for the same reason as my
patch (that flag is supported with GCC 5.1.0) then this patch can be
applied without any issues.
Cheers,
Nathan
prev parent reply other threads:[~2021-12-13 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 4:05 [PATCH v2] MIPS: Makefile: Remove "ifdef need-compiler" for Kbuild.platforms Tiezhu Yang
2021-12-10 16:22 ` Nathan Chancellor
2021-12-10 16:39 ` Masahiro Yamada
2021-12-13 0:35 ` Ryutaroh Matsumoto
2021-12-13 2:09 ` Nathan Chancellor [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=YbarSpe7zhTi+2h4@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=jason@bluehome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ryutaroh@ict.e.titech.ac.jp \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).