All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: nm@ti.com
Cc: Aurelien Jacquiot <a-jacquiot@ti.com>,
	linux-c6x-dev@linux-c6x.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] C6x: time: Ensure consistency in __init
Date: Thu, 26 Mar 2015 10:17:07 -0400	[thread overview]
Message-ID: <1427379427.9430.44.camel@deneb.redhat.com> (raw)
In-Reply-To: <5510AF6B.6030907@ti.com>

On Mon, 2015-03-23 at 19:27 -0500, Nishanth Menon wrote:
> Hi,
> 
> On 03/07/2015 03:39 AM, Nishanth Menon wrote:
> > time_init invokes timer64_init (which is __init annotation)
> > since all of these are invoked at init time, lets maintain
> > consistency by ensuring time_init is marked appropriately
> > as well.
> > 
> > This fixes the following warning with CONFIG_DEBUG_SECTION_MISMATCH=y
> > 
> > WARNING: vmlinux.o(.text+0x3bfc): Section mismatch in reference from the function time_init() to the function .init.text:timer64_init()
> > The function time_init() references
> > the function __init timer64_init().
> > This is often because time_init lacks a __init
> > annotation or the annotation of timer64_init is wrong.
> > 
> > Fixes: 546a39546c64 ("C6X: time management")
> > Signed-off-by: Nishanth Menon <nm@ti.com>
> > ---
> > 
> > Newbie warning: this is my first foray at c6x, So, appreciate a little
> > gentleness while killing me ;)
> > 
> > Applies on latest master:
> > af13e867133a Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux
> > 
> 
> Gentle ping.

Thanks! I added this to the c6x tree for next merge window.

> 
> > 
> >  arch/c6x/kernel/time.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/c6x/kernel/time.c b/arch/c6x/kernel/time.c
> > index 356ee84cad95..04845aaf5985 100644
> > --- a/arch/c6x/kernel/time.c
> > +++ b/arch/c6x/kernel/time.c
> > @@ -49,7 +49,7 @@ u64 sched_clock(void)
> >  	return (tsc * sched_clock_multiplier) >> SCHED_CLOCK_SHIFT;
> >  }
> >  
> > -void time_init(void)
> > +void __init time_init(void)
> >  {
> >  	u64 tmp = (u64)NSEC_PER_SEC << SCHED_CLOCK_SHIFT;
> >  
> > 
> --
> Regards,
> Nishanth Menon



      reply	other threads:[~2015-03-26 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07  9:39 [PATCH] C6x: time: Ensure consistency in __init Nishanth Menon
2015-03-24  0:27 ` Nishanth Menon
2015-03-26 14:17   ` Mark Salter [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=1427379427.9430.44.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=a-jacquiot@ti.com \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.