public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mfd: db8500-prcmu: Fix some section annotations
Date: Thu, 25 Oct 2018 09:03:30 +0100	[thread overview]
Message-ID: <20181025080330.GI4939@dell> (raw)
In-Reply-To: <20181018005628.8295-1-natechancellor@gmail.com>

On Wed, 17 Oct 2018, Nathan Chancellor wrote:

> When building the kernel with Clang, the following section mismatch
> warnings appear:
> 
> WARNING: vmlinux.o(.text+0x7239cc): Section mismatch in reference from
> the function db8500_prcmu_probe() to the function
> .init.text:init_prcm_registers()
> The function db8500_prcmu_probe() references
> the function __init init_prcm_registers().
> This is often because db8500_prcmu_probe lacks a __init
> annotation or the annotation of init_prcm_registers is wrong.
> 
> WARNING: vmlinux.o(.text+0x723e28): Section mismatch in reference from
> the function db8500_prcmu_probe() to the function
> .init.text:fw_project_name()
> The function db8500_prcmu_probe() references
> the function __init fw_project_name().
> This is often because db8500_prcmu_probe lacks a __init
> annotation or the annotation of fw_project_name is wrong.
> 
> db8500_prcmu_probe should not be marked as __init so remove the __init
> annotation from fw_project_name and init_prcm_registers.
> 
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>  drivers/mfd/db8500-prcmu.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Applied for v4.21, thanks.

-- 
Lee Jones [???]
Linaro Services Technical Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2018-10-25  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  0:56 [PATCH] mfd: db8500-prcmu: Fix some section annotations Nathan Chancellor
2018-10-25  8:03 ` Lee Jones [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=20181025080330.GI4939@dell \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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