From: yamada.masahiro@socionext.com (Masahiro Yamada)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: uniphier: initialize outer cache for secondary CPUs
Date: Thu, 31 Mar 2016 19:25:35 +0900 [thread overview]
Message-ID: <CAK7LNAS5AE9daz5F8OKAWgPHKGLB-px3-yi-hgSBfjjAUyxYnQ@mail.gmail.com> (raw)
In-Reply-To: <3226381.VKfgCFa2AC@wuerfel>
Hi Arnd,
2016-03-29 17:11 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> On Tuesday 29 March 2016 15:59:00 kbuild test robot wrote:
>>
>> All warnings (new ones prefixed by >>):
>>
>> >> WARNING: vmlinux.o(.text+0x557b4): Section mismatch in reference from the function uniphier_cache_secondary_init() to the function .init.text:uniphier_cache_activate_all_ways()
>> The function uniphier_cache_secondary_init() references
>> the function __init uniphier_cache_activate_all_ways().
>> This is often because uniphier_cache_secondary_init lacks a __init
>> annotation or the annotation of uniphier_cache_activate_all_ways is wrong.
>>
>
>
> I guess the former: uniphier_cache_secondary_init should be __init, as it will
> only be run at boot time.
>
> Please resend both patches.
>
I think the alternative solution suggested by Russell is much better.
I hope Russell will apply his one, and then I retract this series.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2016-03-31 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 1:38 [PATCH 0/2] ARM: uniphier: updates for Linux 4.7-rc1 Masahiro Yamada
2016-03-29 1:38 ` [PATCH 1/2] ARM: uniphier: fix up cache ops broadcast of ACTLR Masahiro Yamada
2016-03-29 10:03 ` Russell King - ARM Linux
2016-03-30 7:01 ` Masahiro Yamada
2016-03-29 1:38 ` [PATCH 2/2] ARM: uniphier: initialize outer cache for secondary CPUs Masahiro Yamada
2016-03-29 7:59 ` kbuild test robot
2016-03-29 8:11 ` Arnd Bergmann
2016-03-31 10:25 ` Masahiro Yamada [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=CAK7LNAS5AE9daz5F8OKAWgPHKGLB-px3-yi-hgSBfjjAUyxYnQ@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--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).