From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: sunxi: ccu-sun5i needs nkmp
Date: Mon, 20 Mar 2017 10:51:08 +0100 [thread overview]
Message-ID: <20170320095108.nru6wnl5lcigzsoc@lukather> (raw)
In-Reply-To: <CAK8P3a13rqommB90NP_aNPgcoYXb9u=LYs7ep3U=c3C6-3wPHA@mail.gmail.com>
Hi Arnd,
On Mon, Mar 13, 2017 at 05:24:10PM +0100, Arnd Bergmann wrote:
> On Thu, Feb 16, 2017 at 6:53 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> > On Tue, Feb 14, 2017 at 10:29:45PM +0100, Arnd Bergmann wrote:
> >> A randconfig build ran into this rare link error:
> >>
> >> drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.1+0x4): undefined reference to `ccu_nkmp_ops'
> >> drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.7+0x4): undefined reference to `ccu_nkmp_ops'
> >>
> >> This adds the missing 'select'.
> >>
> >> Fixes: 5e73761786d6 ("clk: sunxi-ng: Add sun5i CCU driver")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > Queued as a fix for 4.11, thanks!
>
> I just checked my old patches and this seems to still be required as of
> 4.11-rc2. I see it in linux-next through sunxi/sunxi/for-next, but not as
> part of a clk-fixes merge.
Sorry, I went to holidays without sending the PR. I just did,
hopefully, it should be on Linus' way for the next rc.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170320/8904798f/attachment.sig>
prev parent reply other threads:[~2017-03-20 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 21:29 [PATCH] clk: sunxi: ccu-sun5i needs nkmp Arnd Bergmann
2017-02-16 17:53 ` Maxime Ripard
2017-03-13 16:24 ` Arnd Bergmann
2017-03-20 9:51 ` Maxime Ripard [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=20170320095108.nru6wnl5lcigzsoc@lukather \
--to=maxime.ripard@free-electrons.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