From: Macpaul Lin <macpaul.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>, <Weiyi.lu@mediatek.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mars Cheng <mars.cheng@mediatek.com>,
"Owen Chen" <owen.chen@mediatek.com>
Subject: Re: linux-next: build failure after merge of the mediatek tree
Date: Mon, 16 Dec 2019 17:19:15 +0800 [thread overview]
Message-ID: <1576487955.30597.4.camel@mtkswgap22> (raw)
In-Reply-To: <a2518673-f77f-806c-0bd0-dfb2f6f64da2@gmail.com>
On Mon, 2019-12-16 at 09:49 +0100, Matthias Brugger wrote:
> Hi Stephen,
>
> On 15/12/2019 23:03, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the mediatek tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > drivers/soc/mediatek/mtk-scpsys.c:773:4: error: 'const struct scp_domain_data' has no member named 'subsys_clk_prefix'
> > 773 | .subsys_clk_prefix = "isp",
> > | ^~~~~~~~~~~~~~~~~
[Deleted...]
> > Caused by commit
> >
> > 3742fd77013f ("soc: mediatek: add MT6765 scpsys and subdomain support")
> >
> > I have used the mediatek tree from next-20191213 for today.
> >
>
> Thanks for the heads-up. I dropped the patch for now until it's dependencies are
> all merged. Sorry for the oversight.
>
> Regards
> Matthias
Hi Mathhias,
According to the build error, it looks like this patch has a dependency
with the patch https://patchwork.kernel.org/patch/11118347/ .
The patch "[v7,10/13] soc: mediatek: Add subsys clock control for bus
protection" introduced member subsys_clk_prefix and other required
members.
Thanks!
Regards,
Macpaul Lin
next prev parent reply other threads:[~2019-12-16 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 22:03 linux-next: build failure after merge of the mediatek tree Stephen Rothwell
2019-12-16 8:49 ` Matthias Brugger
2019-12-16 9:19 ` Macpaul Lin [this message]
2022-08-29 23:42 Stephen Rothwell
2022-08-30 11:10 ` 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
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
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=1576487955.30597.4.camel@mtkswgap22 \
--to=macpaul.lin@mediatek.com \
--cc=Weiyi.lu@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mars.cheng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=owen.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).