From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build failure after merge of the scmi tree
Date: Thu, 9 Jul 2020 09:58:02 +1000 [thread overview]
Message-ID: <20200709095802.43bdd86a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi all,
After merging the scmi tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/clk/clk-scmi.c: In function 'scmi_clk_ops_init':
drivers/clk/clk-scmi.c:126:39: error: expected ';' before 'max_rate'
126 | min_rate = sclk->info->list.rates[0]
| ^
| ;
127 | max_rate = sclk->info->list.rates[num_rates - 1];
| ~~~~~~~~
Caused by commit
2a3dd29cd558 ("clk: scmi: Fix min and max rate when registering clocks with discrete rates")
I have used the scmi tree from next-20200708 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-08 23:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 23:58 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-01 0:36 linux-next: build failure after merge of the scmi tree Stephen Rothwell
2022-07-01 8:13 ` Sudeep Holla
2022-11-08 22:29 Stephen Rothwell
2022-11-09 8:58 ` Sudeep Holla
2023-10-05 23:39 Stephen Rothwell
2023-10-06 6:50 ` Sudeep Holla
2023-11-30 21:59 Stephen Rothwell
2023-11-30 22:01 ` Sudeep Holla
2024-08-28 0:15 Stephen Rothwell
2024-08-28 5:29 ` Peng Fan
2024-08-28 8:48 ` Sudeep Holla
2025-05-02 9:37 Stephen Rothwell
2025-05-02 9:44 ` Sudeep Holla
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=20200709095802.43bdd86a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sudeep.holla@arm.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.