From: kernel test robot <lkp@intel.com>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
heikki.krogerus@linux.intel.com, tzungbi@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jthies@google.com, pmalani@chromium.org, akuchynski@google.com,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] platform/chrome: cros_ec_typec: Displayport support
Date: Sat, 28 Sep 2024 12:27:11 +0800 [thread overview]
Message-ID: <202409281250.dtPQ2TrT-lkp@intel.com> (raw)
In-Reply-To: <20240925092505.6.I142fc0c09df58689b98f0cebf1c5e48b9d4fa800@changeid>
Hi Abhishek,
kernel test robot noticed the following build warnings:
[auto build test WARNING on chrome-platform/for-next]
[also build test WARNING on chrome-platform/for-firmware-next usb/usb-testing usb/usb-next usb/usb-linus linus/master v6.11 next-20240927]
[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/Abhishek-Pandit-Subedi/usb-typec-Add-driver-for-Thunderbolt-3-Alternate-Mode/20240926-002931
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
patch link: https://lore.kernel.org/r/20240925092505.6.I142fc0c09df58689b98f0cebf1c5e48b9d4fa800%40changeid
patch subject: [PATCH 6/8] platform/chrome: cros_ec_typec: Displayport support
config: i386-randconfig-001-20240928 (https://download.01.org/0day-ci/archive/20240928/202409281250.dtPQ2TrT-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409281250.dtPQ2TrT-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409281250.dtPQ2TrT-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/platform/chrome/cros_ec_typec.c:21:
>> drivers/platform/chrome/cros_typec_altmode.h:21:1: warning: no previous prototype for function 'cros_typec_register_displayport' [-Wmissing-prototypes]
21 | cros_typec_register_displayport(struct cros_typec_port *port,
| ^
drivers/platform/chrome/cros_typec_altmode.h:20:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
20 | struct typec_altmode *
| ^
| static
>> drivers/platform/chrome/cros_typec_altmode.h:28:5: warning: no previous prototype for function 'cros_typec_displayport_status_update' [-Wmissing-prototypes]
28 | int cros_typec_displayport_status_update(struct typec_altmode *altmode,
| ^
drivers/platform/chrome/cros_typec_altmode.h:28:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
28 | int cros_typec_displayport_status_update(struct typec_altmode *altmode,
| ^
| static
2 warnings generated.
vim +/cros_typec_register_displayport +21 drivers/platform/chrome/cros_typec_altmode.h
10
11 #if IS_ENABLED(CONFIG_TYPEC_DP_ALTMODE)
12 struct typec_altmode *
13 cros_typec_register_displayport(struct cros_typec_port *port,
14 struct typec_altmode_desc *desc,
15 bool ap_mode_entry);
16
17 int cros_typec_displayport_status_update(struct typec_altmode *altmode,
18 struct typec_displayport_data *data);
19 #else
20 struct typec_altmode *
> 21 cros_typec_register_displayport(struct cros_typec_port *port,
22 struct typec_altmode_desc *desc,
23 bool ap_mode_entry)
24 {
25 return typec_port_register_altmode(port->port, desc);
26 }
27
> 28 int cros_typec_displayport_status_update(struct typec_altmode *altmode,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-28 4:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:25 [PATCH 0/8] Thunderbolt and DP altmode support for cros-ec-typec Abhishek Pandit-Subedi
2024-09-25 16:25 ` [PATCH 1/8] usb: typec: Add driver for Thunderbolt 3 Alternate Mode Abhishek Pandit-Subedi
2024-09-26 14:06 ` Heikki Krogerus
2024-09-26 15:14 ` kernel test robot
2024-09-25 16:25 ` [PATCH 2/8] usb: typec: altmode_match should handle TYPEC_ANY_MODE Abhishek Pandit-Subedi
2024-09-25 16:54 ` Dmitry Baryshkov
2024-09-25 17:31 ` Abhishek Pandit-Subedi
2024-09-26 14:35 ` Heikki Krogerus
2024-09-25 16:25 ` [PATCH 3/8] usb: typec: intel_pmc_mux: Null check before use Abhishek Pandit-Subedi
2024-09-25 16:54 ` Dmitry Baryshkov
2024-09-25 17:29 ` Abhishek Pandit-Subedi
2024-09-26 14:37 ` Heikki Krogerus
2024-09-25 16:25 ` [PATCH 4/8] usb: typec: Auto enter control for alternate modes Abhishek Pandit-Subedi
2024-09-25 16:25 ` [PATCH 5/8] platform/chrome: cros_ec_typec: Update partner altmode active Abhishek Pandit-Subedi
2024-09-26 14:48 ` Heikki Krogerus
2024-09-25 16:25 ` [PATCH 6/8] platform/chrome: cros_ec_typec: Displayport support Abhishek Pandit-Subedi
2024-09-26 14:39 ` Heikki Krogerus
2024-09-27 9:07 ` Dmitry Baryshkov
2024-09-28 4:27 ` kernel test robot [this message]
2024-09-25 16:25 ` [PATCH 7/8] platform/chrome: cros_ec_typec: Thunderbolt support Abhishek Pandit-Subedi
2024-09-25 17:13 ` Dmitry Baryshkov
2024-09-25 18:42 ` Abhishek Pandit-Subedi
2024-09-25 21:20 ` Dmitry Baryshkov
2024-09-25 21:35 ` Abhishek Pandit-Subedi
2024-09-26 14:32 ` kernel test robot
2024-09-27 7:34 ` kernel test robot
2024-09-25 16:25 ` [PATCH 8/8] platform/chrome: cros_ec_typec: Disable auto_enter Abhishek Pandit-Subedi
2024-09-25 17:03 ` Dmitry Baryshkov
2024-09-25 17:39 ` Abhishek Pandit-Subedi
2024-09-25 21:24 ` Dmitry Baryshkov
2024-09-25 21:35 ` Abhishek Pandit-Subedi
2024-09-25 21:43 ` Dmitry Baryshkov
2024-09-25 17:12 ` [PATCH 0/8] Thunderbolt and DP altmode support for cros-ec-typec Dmitry Baryshkov
2024-09-25 17:20 ` Abhishek Pandit-Subedi
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=202409281250.dtPQ2TrT-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@google.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmalani@chromium.org \
--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