From: Kishon Vijay Abraham I <kishon@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Meng Dongyang <daniel.meng@rock-chips.com>
Subject: Re: linux-next: build failure after merge of the phy-next tree
Date: Thu, 30 Mar 2017 11:09:11 +0530 [thread overview]
Message-ID: <d9371bdc-4eb1-5bf0-6060-972e96daedf4@ti.com> (raw)
In-Reply-To: <20170330144735.534101e7@canb.auug.org.au>
Hi,
On Thursday 30 March 2017 09:17 AM, Stephen Rothwell wrote:
> Hi Kishon,
>
> After merging the phy-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/phy/phy-rockchip-inno-usb2.c:1148:3: error: unknown field 'phy_tuning' specified in initializer
> .phy_tuning = rk3328_usb2phy_tuning,
> ^
> drivers/phy/phy-rockchip-inno-usb2.c:1148:17: error: 'rk3328_usb2phy_tuning' undeclared here (not in a function)
> .phy_tuning = rk3328_usb2phy_tuning,
> ^
>
> Caused by commit
>
> ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328")
>
> I have used the phy-next tree from next-20170329 for today.
Thanks for reporting this. Will fix it in my tree.
-Kishon
next prev parent reply other threads:[~2017-03-30 5:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 3:47 linux-next: build failure after merge of the phy-next tree Stephen Rothwell
2017-03-30 5:39 ` Kishon Vijay Abraham I [this message]
2019-08-27 5:50 Stephen Rothwell
2020-11-17 2:40 Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18 2:56 ` Stephen Rothwell
2020-11-18 4:23 ` Vinod Koul
2020-12-01 6:07 Stephen Rothwell
2020-12-01 6:45 ` Sergio Paracuellos
2020-12-01 10:39 ` Vinod Koul
2021-12-15 13:49 broonie
2021-12-15 14:14 ` Marcel Ziswiler
2021-12-15 15:20 ` Vinod Koul
2021-12-24 3:03 Stephen Rothwell
2021-12-24 4:37 ` Vinod Koul
2022-07-07 5:39 Stephen Rothwell
2022-07-07 5:53 ` Vinod Koul
2023-02-13 2:55 Stephen Rothwell
2023-02-13 5:17 ` Vinod Koul
2023-08-18 5:40 Stephen Rothwell
2023-08-22 14:00 ` Vinod Koul
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=d9371bdc-4eb1-5bf0-6060-972e96daedf4@ti.com \
--to=kishon@ti.com \
--cc=daniel.meng@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).