linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the compiler-attributes tree
Date: Thu, 7 Feb 2019 08:30:57 +1100	[thread overview]
Message-ID: <20190207083057.05b40e61@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

Hi Miguel,

After merging the compiler-attributes tree, today's linux-next build
(arm multi_v7_defconfig) failed like this:

In file included from arch/arm/crypto/aes-neonbs-glue.c:17:
include/linux/module.h:138:7: error: section of alias 'cleanup_module' must match section of its target
  void cleanup_module(void) __exit __attribute__((alias(#exitfn)));
       ^~~~~~~~~~~~~~
arch/arm/crypto/aes-neonbs-glue.c:433:1: note: in expansion of macro 'module_exit'
 module_exit(aes_exit);
 ^~~~~~~~~~~

Caused by commit

  b31ca3fcca36 ("include/linux/module.h: mark init/cleanup_module aliases as __init/exit")

I have used the compiler-attributes tree from next-20190206 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-02-06 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 21:30 Stephen Rothwell [this message]
2019-02-06 21:48 ` linux-next: build failure after merge of the compiler-attributes tree Miguel Ojeda
2019-08-29 22:52 Stephen Rothwell
2019-08-29 22:53 ` Nick Desaulniers
2019-08-29 22:54 ` Miguel Ojeda
2019-08-29 22:58   ` Miguel Ojeda

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=20190207083057.05b40e61@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.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 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).