From: kernel test robot <lkp@intel.com>
To: Prashant Malani <pmalani@chromium.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
chrome-platform@lists.linux.dev
Cc: kbuild-all@lists.01.org, bleung@chromium.org,
heikki.krogerus@linux.intel.com,
Prashant Malani <pmalani@chromium.org>,
Daisuke Nojiri <dnojiri@chromium.org>,
"Dustin L. Howett" <dustin@howett.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <groeck@chromium.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Tzung-Bi Shih <tzungbi@kernel.org>
Subject: Re: [PATCH v2 6/9] platform/chrome: cros_typec_switch: Add event check
Date: Thu, 7 Jul 2022 12:25:51 +0800 [thread overview]
Message-ID: <202207071256.63ElDHIG-lkp@intel.com> (raw)
In-Reply-To: <20220706171601.807042-7-pmalani@chromium.org>
Hi Prashant,
I love your patch! Perhaps something to improve:
[auto build test WARNING on usb/usb-testing]
[cannot apply to chrome-platform/for-next linus/master balbi-usb/testing/next peter-chen-usb/for-usb-next v5.19-rc5]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Prashant-Malani/platform-chrome-Type-C-switch-driver-and-Type-C-framework-updates/20220707-012614
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220707/202207071256.63ElDHIG-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/60e03c1b36c0e3533e481b44152faab38448be5b
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Prashant-Malani/platform-chrome-Type-C-switch-driver-and-Type-C-framework-updates/20220707-012614
git checkout 60e03c1b36c0e3533e481b44152faab38448be5b
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/platform/chrome/ kernel/bpf/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/platform/chrome/cros_typec_switch.c:81:6: warning: no previous prototype for 'cros_typec_check_event' [-Wmissing-prototypes]
81 | bool cros_typec_check_event(struct cros_typec_switch_data *sdata, int port_num, u32 mask)
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/platform/chrome/cros_typec_switch.c:159:6: warning: no previous prototype for 'cros_typec_unregister_switches' [-Wmissing-prototypes]
159 | void cros_typec_unregister_switches(struct cros_typec_switch_data *sdata)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/platform/chrome/cros_typec_switch.c:170:5: warning: no previous prototype for 'cros_typec_register_retimer' [-Wmissing-prototypes]
170 | int cros_typec_register_retimer(struct cros_typec_port *port, struct fwnode_handle *fwnode)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/cros_typec_check_event +81 drivers/platform/chrome/cros_typec_switch.c
80
> 81 bool cros_typec_check_event(struct cros_typec_switch_data *sdata, int port_num, u32 mask)
82 {
83 struct ec_response_typec_status resp;
84 struct ec_params_typec_status req = {
85 .port = port_num,
86 };
87 int ret;
88
89 ret = cros_ec_command(sdata->ec, 0, EC_CMD_TYPEC_STATUS, &req, sizeof(req),
90 &resp, sizeof(resp));
91 if (ret < 0) {
92 dev_warn(sdata->dev, "EC_CMD_TYPEC_STATUS failed for port: %d\n", port_num);
93 return false;
94 }
95
96 if (resp.events & mask)
97 return true;
98
99 return false;
100 }
101
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-07 4:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 17:15 [PATCH v2 0/9] platform/chrome: Type-C switch driver and Type-C framework updates Prashant Malani
2022-07-06 17:15 ` [PATCH v2 1/9] usb: typec: Add support for retimers Prashant Malani
2022-07-06 17:15 ` [PATCH v2 2/9] usb: typec: Add retimer handle to port Prashant Malani
2022-07-06 17:15 ` [PATCH v2 3/9] platform/chrome: Add Type-C mux set command definitions Prashant Malani
2022-07-06 17:15 ` [PATCH v2 4/9] platform/chrome: cros_typec_switch: Add switch driver Prashant Malani
2022-07-07 0:29 ` kernel test robot
2022-07-06 17:15 ` [PATCH v2 5/9] platform/chrome: cros_typec_switch: Set EC retimer Prashant Malani
2022-07-06 17:15 ` [PATCH v2 6/9] platform/chrome: cros_typec_switch: Add event check Prashant Malani
2022-07-07 4:25 ` kernel test robot [this message]
2022-07-07 22:06 ` Prashant Malani
2022-07-06 17:15 ` [PATCH v2 7/9] platform/chrome: cros_typec_switch: Register mode switches Prashant Malani
2022-07-06 17:15 ` [PATCH v2 8/9] platform/chrome: cros_ec_typec: Cleanup switch handle return paths Prashant Malani
2022-07-06 17:15 ` [PATCH v2 9/9] platform/chrome: cros_ec_typec: Get retimer handle 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=202207071256.63ElDHIG-lkp@intel.com \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dnojiri@chromium.org \
--cc=dustin@howett.net \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gustavoars@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=sebastian.reichel@collabora.com \
--cc=tzungbi@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).