From: kbuild test robot <lkp@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
David Miller <davem@davemloft.net>,
devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Miroslav Lichvar <mlichvar@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH V5 net-next 5/6] net: mdio: of: Register discovered MII time stampers.
Date: Sat, 1 Jun 2019 01:24:00 +0800 [thread overview]
Message-ID: <201906010128.tXc0Y24Z%lkp@intel.com> (raw)
In-Reply-To: <a375c2b73288184fe86155707ba150daaf946943.1559281985.git.richardcochran@gmail.com>
Hi Richard,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Richard-Cochran/Peer-to-Peer-One-Step-time-stamping/20190531-200348
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/of/of_mdio.c:46:24: sparse: sparse: symbol 'of_find_mii_timestamper' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2019-05-31 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 5:56 [PATCH V5 net-next 0/6] Peer to Peer One-Step time stamping Richard Cochran
2019-05-31 5:56 ` [PATCH V5 net-next 1/6] net: Introduce peer to peer one step PTP " Richard Cochran
2019-05-31 5:56 ` [PATCH V5 net-next 2/6] net: Introduce a new MII time stamping interface Richard Cochran
2019-05-31 5:56 ` [PATCH V5 net-next 3/6] net: Add a layer for non-PHY MII time stamping drivers Richard Cochran
2019-05-31 5:56 ` [PATCH V5 net-next 4/6] dt-bindings: ptp: Introduce MII time stamping devices Richard Cochran
2019-07-08 21:38 ` Rob Herring
2019-07-09 5:11 ` Richard Cochran
2019-05-31 5:56 ` [PATCH V5 net-next 5/6] net: mdio: of: Register discovered MII time stampers Richard Cochran
2019-05-31 17:24 ` kbuild test robot [this message]
2019-05-31 17:24 ` [RFC PATCH] net: mdio: of: of_find_mii_timestamper() can be static kbuild test robot
2019-05-31 5:56 ` [PATCH V5 net-next 6/6] ptp: Add a driver for InES time stamping IP core Richard Cochran
2019-05-31 20:22 ` kbuild test robot
2019-05-31 20:22 ` [RFC PATCH] ptp: ines_ptp_probe_channel() can be static kbuild test robot
2019-05-31 21:54 ` [PATCH V5 net-next 0/6] Peer to Peer One-Step time stamping David Miller
2019-06-01 0:13 ` David Miller
2019-06-01 5:09 ` Richard Cochran
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=201906010128.tXc0Y24Z%lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=kbuild-all@01.org \
--cc=mark.rutland@arm.com \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).