From: Dmitry Osipenko <digetx@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-tegra <linux-tegra@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>
Subject: Re: Build regressions/improvements in v5.5-rc1
Date: Mon, 9 Dec 2019 15:45:17 +0300 [thread overview]
Message-ID: <33f03ef9-c868-8bd5-ae5d-3da703d21fa9@gmail.com> (raw)
In-Reply-To: <CAMuHMdV+4Q2atJUPsYuc+UFxyoh1fscQL7aLUp4CWrb7=U706g@mail.gmail.com>
09.12.2019 14:02, Geert Uytterhoeven пишет:
> On Mon, Dec 9, 2019 at 11:57 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>> Below is the list of build error/warning regressions/improvements in
>> v5.5-rc1[1] compared to v5.4[2].
>>
>> Summarized:
>> - build errors: +2/-8
>> - build warnings: +84/-87
>>
>> Happy fixing! ;-)
>>
>> Thanks to the linux-next team for providing the build service.
>>
>> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/e42617b825f8073569da76dc4510bfa019b1c35a/ (all 232 configs)
>> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/219d54332a09e8d8741c1e1982f5eae56099de85/ (all 232 configs)
>>
>>
>> *** ERRORS ***
>>
>> 2 error regressions:
>> + error: "clk_set_min_rate" [drivers/devfreq/tegra30-devfreq.ko] undefined!: => N/A
>> + error: tegra30-devfreq.c: undefined reference to `clk_set_min_rate': => .text+0xcc8)
>
> sh-all{mod,yes}config
>
> Legacy non-CCF platform do not provide clk_set_min_rate(), so this needs
> a dependency on CCF.
Hello Geert,
Thanks for the report, I'll make a patch to fix it.
> BTW, it seems this was already known back in June...
> https://lore.kernel.org/linux-pm/5301c593-97e1-db4e-067b-0522537b55d9@gmail.com/
Yes, I was a bit confused about why only T20 driver was causing the
trouble.
prev parent reply other threads:[~2019-12-09 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 10:56 Geert Uytterhoeven
2019-12-09 11:02 ` Geert Uytterhoeven
2019-12-09 12:45 ` Dmitry Osipenko [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=33f03ef9-c868-8bd5-ae5d-3da703d21fa9@gmail.com \
--to=digetx@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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
all inboxes | Powered by JetHome®