linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: ux500: Silence compiler warnings due to missing __cpuinitdata
Date: Tue, 4 Jun 2013 17:38:19 +0100	[thread overview]
Message-ID: <20130604163819.GO3370@gmail.com> (raw)
In-Reply-To: <1916856.3pBBOMscik@wuerfel>

On Tue, 04 Jun 2013, Arnd Bergmann wrote:

> On Tuesday 04 June 2013 16:36:48 Lee Jones wrote:
> > WARNING: vmlinux.o(.text.unlikely+0x25c): Section mismatch in reference \
> >   from the function write_pen_release() to the variable                 \
> >   .cpuinit.data:pen_release
> > The function write_pen_release() references
> > the variable __cpuinitdata pen_release.
> > This is often because write_pen_release lacks a __cpuinitdata
> > 
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> 
> I don't see bug on my machine. Are you sure it's not already fixed in 
> a different way in linux-next?

It's a possibility.

Basically I have a v3.10-rc3 kernel and I did:

`git checkout next/master -- scripts`

I assumed some extra checking appeared in the scripts directory, so I
just fixed the warnings and sent out a patch.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2013-06-04 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 15:36 [PATCH 1/2] ARM: ux500: Silence compiler warnings due to missing ux500_read_asicid() __init Lee Jones
2013-06-04 15:36 ` [PATCH 2/2] ARM: ux500: Silence compiler warnings due to missing __cpuinitdata Lee Jones
2013-06-04 15:57   ` Arnd Bergmann
2013-06-04 16:38     ` Lee Jones [this message]
2013-06-04 15:55 ` [PATCH 1/2] ARM: ux500: Silence compiler warnings due to missing ux500_read_asicid() __init Arnd Bergmann
2013-06-05 12:32   ` Linus Walleij

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=20130604163819.GO3370@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).