From: kernel test robot <lkp@intel.com>
To: Parshuram Thombare <pthombar@cadence.com>,
robert.foss@linaro.org, robh+dt@kernel.org,
laurent.pinchart@ideasonboard.com, airlied@linux.ie,
daniel@ffwll.ch
Cc: kbuild-all@lists.01.org, devicetree@vger.kernel.org,
narmstrong@baylibre.com,
Parshuram Thombare <pthombar@cadence.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm: bridge: cdns-mhdp8546: Enable HDCP
Date: Thu, 18 Mar 2021 08:38:47 +0800 [thread overview]
Message-ID: <202103180808.S467FFN7-lkp@intel.com> (raw)
In-Reply-To: <1615997158-16737-1-git-send-email-pthombar@cadence.com>
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
Hi Parshuram,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linux/master linus/master v5.12-rc3 next-20210317]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Parshuram-Thombare/enable-HDCP-in-Cadence-MHDP-bridge-driver/20210318-000928
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: x86_64-randconfig-s022-20210317 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-277-gc089cd2d-dirty
# https://github.com/0day-ci/linux/commit/9c8eb15a5059a553e08304619775dd7af4394eb1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Parshuram-Thombare/enable-HDCP-in-Cadence-MHDP-bridge-driver/20210318-000928
git checkout 9c8eb15a5059a553e08304619775dd7af4394eb1
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-hdcp.c:502:5: sparse: sparse: symbol 'cdns_mhdp_hdcp_set_lc' was not declared. Should it be static?
>> drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-hdcp.c:516:1: sparse: sparse: symbol 'cdns_mhdp_hdcp_set_public_key_params' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38123 bytes --]
next prev parent reply other threads:[~2021-03-18 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 16:04 [PATCH v3 0/2] enable HDCP in Cadence MHDP bridge driver Parshuram Thombare
2021-03-17 16:05 ` [PATCH v3 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding changes for HDCP Parshuram Thombare
2021-03-17 16:05 ` [PATCH v3 2/2] drm: bridge: cdns-mhdp8546: Enable HDCP Parshuram Thombare
2021-03-17 20:29 ` kernel test robot
2021-03-18 0:38 ` kernel test robot [this message]
2021-03-18 0:38 ` [RFC PATCH] drm: bridge: cdns-mhdp8546: cdns_mhdp_hdcp_set_lc() can be static 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=202103180808.S467FFN7-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=pthombar@cadence.com \
--cc=robert.foss@linaro.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).