public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-mips@vger.kernel.org, llvm@lists.linux.dev,
	"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
	"Nick Desaulniers" <ndesaulniers@google.com>,
	"Phil Mathieu-Daudé" <philmd@linaro.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: next: mips: ERROR: modpost: Section mismatches detected.
Date: Thu, 20 Apr 2023 08:45:37 -0700	[thread overview]
Message-ID: <20230420154537.GA706381@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CA+G9fYt+4e57Gdy6cix=LeNK6XqWoui8du=mZWu=cf8vPYocKw@mail.gmail.com>

Hi Naresh,

On Thu, Apr 20, 2023 at 04:31:12PM +0530, Naresh Kamboju wrote:
> Following build failures noticed on Linux next-20230419 for mips.
> 
> Regressions found on mips:
>  - build/clang-nightly-allnoconfig
>  - build/clang-16-allnoconfig
>  - build/clang-16-tinyconfig
>  - build/clang-nightly-tinyconfig
> 
> 
> arch/mips/kernel/genex.S:520:2: warning: macro defined with named
> parameters which are not used in macro body, possible positional
> parameter found in body which will have no effect
>  .macro __BUILD_verbose nexception
>  ^
> WARNING: modpost: vmlinux.o: section mismatch in reference: check_bugs
> (section: .text) -> check_bugs32 (section: .init.text)
> ERROR: modpost: Section mismatches detected.
> Set CONFIG_SECTION_MISMATCH_WARN_ONLY=y to allow them.
> make[2]: *** [scripts/Makefile.modpost:136: vmlinux.symvers] Error 1
> make[2]: *** Deleting file 'vmlinux.symvers'
> make[2]: Target '__modpost' not remade because of errors.
> make[1]: *** [Makefile:1978: modpost] Error 2

Thanks for the report. I sent a patch for this yesterday:

https://lore.kernel.org/20230419-mips-check_bugs-init-attribute-v1-1-91e6eed55b89@kernel.org/

Cheers,
Nathan

      reply	other threads:[~2023-04-20 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20 11:01 next: mips: ERROR: modpost: Section mismatches detected Naresh Kamboju
2023-04-20 15:45 ` 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=20230420154537.GA706381@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=ndesaulniers@google.com \
    --cc=philmd@linaro.org \
    --cc=tsbogend@alpha.franken.de \
    /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