mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Meng Dongyang <daniel.meng@rock-chips.com>
Cc: kbuild-all@01.org, kishon@ti.com, linux-kernel@vger.kernel.org,
	heiko@sntech.de, linux-usb@vger.kernel.org,
	linux-rockchip@lists.infradead.org, huangtao@rock-chips.com,
	kever.yang@rock-chips.com, william.wu@rock-chips.com,
	frank.wang@rock-chips.com, daniel.meng@rock-chips.com
Subject: Re: [PATCH 2/2] phy: rockchip-inno-usb2: add support of u2phy for rk3328
Date: Sun, 12 Mar 2017 07:00:34 +0800	[thread overview]
Message-ID: <201703120657.NDYLEtsJ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1488363215-26566-3-git-send-email-daniel.meng@rock-chips.com>

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

Hi Meng,

[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.11-rc1 next-20170310]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Meng-Dongyang/add-support-of-u2phy-for-rk3328/20170303-050954
base:   https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

>> drivers/phy/phy-rockchip-inno-usb2.c:1143:3: error: unknown field 'phy_tuning' specified in initializer
      .phy_tuning = rk3328_usb2phy_tuning,
      ^
>> drivers/phy/phy-rockchip-inno-usb2.c:1143:17: error: 'rk3328_usb2phy_tuning' undeclared here (not in a function)
      .phy_tuning = rk3328_usb2phy_tuning,
                    ^

vim +/phy_tuning +1143 drivers/phy/phy-rockchip-inno-usb2.c

  1137	}
  1138	
  1139	static const struct rockchip_usb2phy_cfg rk3328_phy_cfgs[] = {
  1140		{
  1141			.reg = 0x100,
  1142			.num_ports	= 2,
> 1143			.phy_tuning	= rk3328_usb2phy_tuning,
  1144			.clkout_ctl	= { 0x108, 4, 4, 1, 0 },
  1145			.port_cfgs	= {
  1146				[USB2PHY_PORT_HOST] = {

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 48243 bytes --]

  reply	other threads:[~2017-03-11 23:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:13 [PATCH 0/2] " Meng Dongyang
2017-03-01 10:13 ` [PATCH 1/2] Documentation: bindings: add DT documentation for u2phy and u2phy grf Meng Dongyang
2017-03-01 10:13 ` [PATCH 2/2] phy: rockchip-inno-usb2: add support of u2phy for rk3328 Meng Dongyang
2017-03-11 23:00   ` kbuild test robot [this message]
2017-03-27 11:43 ` [PATCH 0/2] " Kishon Vijay Abraham I

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=201703120657.NDYLEtsJ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=daniel.meng@rock-chips.com \
    --cc=frank.wang@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=kbuild-all@01.org \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=william.wu@rock-chips.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 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®