From: Matthias Brugger <matthias.bgg@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mediatek tree
Date: Tue, 30 Aug 2022 13:10:09 +0200 [thread overview]
Message-ID: <18caa4aa-9ed9-b2d8-b375-395b444d0ed5@gmail.com> (raw)
In-Reply-To: <20220830094230.18c76615@canb.auug.org.au>
Hi Stephen,
On 30/08/2022 01:42, Stephen Rothwell wrote:
> Hi all,
>
> After merging the mediatek tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/soc/mediatek/mtk-svs.c: In function 'svs_get_bank_volts_v3':
> drivers/soc/mediatek/mtk-svs.c:887:47: error: implicit declaration of function 'FIELD_GET'; did you mean 'FOLL_GET'? [-Werror=implicit-function-declaration]
> 887 | svsb->volt[turn_pt] = FIELD_GET(SVSB_VOPS_FLD_VOP0_4, vop30);
> | ^~~~~~~~~
> | FOLL_GET
> drivers/soc/mediatek/mtk-svs.c: In function 'svs_set_bank_freq_pct_v2':
> drivers/soc/mediatek/mtk-svs.c:1073:25: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
> 1073 | freqpct74_val = FIELD_PREP(SVSB_FREQPCTS_FLD_PCT0_4, svsb->freq_pct[8]) |
> | ^~~~~~~~~~
>
> Caused by commit
>
> a92438c5a30a ("soc: mediatek: mtk-svs: Use bitfield access macros where possible")
>
> I have used the mediatek tree from next-20220829 for today.
>
Thanks for the information. We were able to identify the issue (not really
difficult) and I pushed a fix to my for-next tree. So we should be good by tomorrow.
Cheers,
Matthias
next prev parent reply other threads:[~2022-08-30 11:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:42 linux-next: build failure after merge of the mediatek tree Stephen Rothwell
2022-08-30 11:10 ` Matthias Brugger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-15 6:30 Stephen Rothwell
2025-04-15 7:27 ` AngeloGioacchino Del Regno
2024-06-17 16:44 Mark Brown
2024-06-18 7:49 ` Julien Panis
2024-06-18 10:03 ` AngeloGioacchino Del Regno
2024-06-18 10:20 ` AngeloGioacchino Del Regno
2024-06-18 16:45 ` Julien Panis
2024-06-18 17:42 ` Mark Brown
2024-06-18 18:03 ` Daniel Lezcano
2024-06-19 7:40 ` AngeloGioacchino Del Regno
2024-07-15 17:11 ` Julien Panis
2024-06-18 17:07 ` Kevin Hilman
2024-06-18 11:51 ` Mark Brown
2023-04-03 8:15 Stephen Rothwell
2023-04-03 8:45 ` AngeloGioacchino Del Regno
2023-04-03 9:41 ` AngeloGioacchino Del Regno
2023-04-10 23:25 ` Stephen Rothwell
2023-04-11 16:53 ` Matthias Brugger
2023-04-03 7:52 Stephen Rothwell
2023-04-03 8:43 ` AngeloGioacchino Del Regno
2023-04-03 10:14 ` Krzysztof Kozlowski
2023-04-10 23:24 ` Stephen Rothwell
2023-04-11 16:52 ` Matthias Brugger
2019-12-15 22:03 Stephen Rothwell
2019-12-16 8:49 ` Matthias Brugger
2019-12-16 9:19 ` Macpaul Lin
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=18caa4aa-9ed9-b2d8-b375-395b444d0ed5@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=sfr@canb.auug.org.au \
/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