From: kbuild test robot <lkp@intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
heikki.krogerus@intel.com, enric.balletbo@collabora.com,
bleung@chromium.org, Prashant Malani <pmalani@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH 1/3] platform/chrome: Add Type C connector class driver
Date: Fri, 7 Feb 2020 14:51:56 +0800 [thread overview]
Message-ID: <202002071406.LXbYPq2Y%lkp@intel.com> (raw)
In-Reply-To: <20200205205954.84503-2-pmalani@chromium.org>
Hi Prashant,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on chrome-platform-linux/for-next]
[also build test WARNING on linux/master linus/master v5.5 next-20200207]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Prashant-Malani/platform-chrome-Add-Type-C-connector-class-driver/20200206-225838
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-159-g100509c0-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/platform/chrome/cros_ec_typec.c:28:5: sparse: sparse: symbol 'cros_typec_parse_port_props' 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
next prev parent reply other threads:[~2020-02-07 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 20:59 [PATCH 0/3] platform/chrome: Add Type C connector class driver Prashant Malani
2020-02-05 20:59 ` [PATCH 1/3] " Prashant Malani
2020-02-06 16:19 ` Enric Balletbo i Serra
2020-02-06 23:30 ` Prashant Malani
2020-02-07 17:00 ` Enric Balletbo i Serra
2020-02-07 20:28 ` Prashant Malani
2020-02-07 6:51 ` kbuild test robot [this message]
2020-02-07 6:52 ` [RFC PATCH] platform/chrome: cros_typec_parse_port_props() can be static kbuild test robot
2020-02-05 20:59 ` [PATCH 2/3] platform/chrome: typec: Get PD_CONTROL cmd version Prashant Malani
2020-02-05 20:59 ` [PATCH 3/3] platform/chrome: typec: Update port info from EC Prashant Malani
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=202002071406.LXbYPq2Y%lkp@intel.com \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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).