From: Dan Murphy <dmurphy@ti.com>
To: kernel test robot <lkp@intel.com>, <andrew@lunn.ch>,
<f.fainelli@gmail.com>, <hkallweit1@gmail.com>,
<davem@davemloft.net>, <robh@kernel.org>
Cc: <kbuild-all@lists.01.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH net-next v8 2/5] net: phy: Add a helper to return the index for of the internal delay
Date: Thu, 18 Jun 2020 18:42:23 -0500 [thread overview]
Message-ID: <83735f8a-efe6-5648-4925-d4a945e0c070@ti.com> (raw)
In-Reply-To: <202006190753.uZWR7VTH%lkp@intel.com>
Hello
On 6/18/20 6:29 PM, kernel test robot wrote:
> Hi Dan,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Dan-Murphy/RGMII-Internal-delay-common-property/20200619-051238
> base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git cb8e59cc87201af93dfbb6c3dccc8fcad72a09c2
> config: i386-defconfig (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
> reproduce (this is a W=1 build):
> # save the attached .config to linux build tree
> make W=1 ARCH=i386
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> drivers/net/phy/phy_device.c: In function 'phy_get_int_delay_property':
>>> drivers/net/phy/phy_device.c:2678:1: error: expected ';' before '}' token
> 2678 | }
> | ^
>
> vim +2678 drivers/net/phy/phy_device.c
>
> 2660
> 2661 #if IS_ENABLED(CONFIG_OF_MDIO)
> 2662 static int phy_get_int_delay_property(struct device *dev, const char *name)
> 2663 {
> 2664 s32 int_delay;
> 2665 int ret;
> 2666
> 2667 ret = device_property_read_u32(dev, name, &int_delay);
> 2668 if (ret)
> 2669 return ret;
> 2670
> 2671 return int_delay;
> 2672 }
> 2673 #else
> 2674 static inline int phy_get_int_delay_property(struct device *dev,
> 2675 const char *name)
> 2676 {
> 2677 return -EINVAL
Ack missed compiling this use case.
Dan
>> 2678 }
> 2679 #endif
> 2680
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2020-06-18 23:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:10 [PATCH net-next v8 0/5] RGMII Internal delay common property Dan Murphy
2020-06-18 21:10 ` [PATCH net-next v8 1/5] dt-bindings: net: Add tx and rx internal delays Dan Murphy
2020-06-18 21:10 ` [PATCH net-next v8 2/5] net: phy: Add a helper to return the index for of the internal delay Dan Murphy
2020-06-18 23:29 ` kernel test robot
2020-06-18 23:42 ` Dan Murphy [this message]
2020-06-19 2:36 ` kernel test robot
2020-06-18 21:10 ` [PATCH net-next v8 3/5] dt-bindings: net: Add RGMII internal delay for DP83869 Dan Murphy
2020-06-18 21:10 ` [PATCH net-next v8 4/5] net: dp83869: Add RGMII internal delay configuration Dan Murphy
2020-06-19 5:14 ` kernel test robot
2020-06-18 21:10 ` [PATCH net-next v8 5/5] net: phy: DP83822: Add setting the fixed internal delay Dan Murphy
2020-06-19 3:27 ` kernel test robot
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=83735f8a-efe6-5648-4925-d4a945e0c070@ti.com \
--to=dmurphy@ti.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
/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