From: kernel test robot <lkp@intel.com>
To: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
heikki.krogerus@linux.intel.com, tzungbi@kernel.org,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev, akuchynski@google.com,
pmalani@chromium.org, jthies@google.com,
dmitry.baryshkov@linaro.org, badhri@google.com,
rdbabiera@google.com,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/7] usb: typec: Add driver for Thunderbolt 3 Alternate Mode
Date: Mon, 9 Dec 2024 12:28:12 +0800 [thread overview]
Message-ID: <202412080010.bWqlreGq-lkp@intel.com> (raw)
In-Reply-To: <20241206153813.v4.2.I3080b036e8de0b9957c57c1c3059db7149c5e549@changeid>
Hi Abhishek,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.12]
[cannot apply to chrome-platform/for-next chrome-platform/for-firmware-next usb/usb-testing usb/usb-next usb/usb-linus masahiroy-kbuild/for-next masahiroy-kbuild/fixes linus/master v6.13-rc1 next-20241206]
[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-Only-use-SVID-for-matching-altmodes/20241207-074104
base: v6.12
patch link: https://lore.kernel.org/r/20241206153813.v4.2.I3080b036e8de0b9957c57c1c3059db7149c5e549%40changeid
patch subject: [PATCH v4 2/7] usb: typec: Add driver for Thunderbolt 3 Alternate Mode
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20241208/202412080010.bWqlreGq-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241208/202412080010.bWqlreGq-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/202412080010.bWqlreGq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/typec/altmodes/thunderbolt.c:16: warning: cannot understand function prototype: 'enum tbt_state '
vim +16 drivers/usb/typec/altmodes/thunderbolt.c
15
> 16 enum tbt_state {
17 TBT_STATE_IDLE,
18 TBT_STATE_SOP_P_ENTER,
19 TBT_STATE_SOP_PP_ENTER,
20 TBT_STATE_ENTER,
21 TBT_STATE_EXIT,
22 TBT_STATE_SOP_PP_EXIT,
23 TBT_STATE_SOP_P_EXIT
24 };
25
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-09 4:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 23:38 [PATCH v4 0/7] Thunderbolt and DP altmode support for cros-ec-typec Abhishek Pandit-Subedi
2024-12-06 23:38 ` [PATCH v4 1/7] usb: typec: Only use SVID for matching altmodes Abhishek Pandit-Subedi
2024-12-11 9:40 ` Heikki Krogerus
2024-12-06 23:38 ` [PATCH v4 2/7] usb: typec: Add driver for Thunderbolt 3 Alternate Mode Abhishek Pandit-Subedi
2024-12-09 4:28 ` kernel test robot [this message]
2024-12-11 0:21 ` Stephen Boyd
2024-12-13 17:55 ` Abhishek Pandit-Subedi
2024-12-06 23:38 ` [PATCH v4 3/7] usb: typec: Print err when displayport fails to enter Abhishek Pandit-Subedi
2024-12-11 10:09 ` Heikki Krogerus
2024-12-06 23:38 ` [PATCH v4 4/7] platform/chrome: cros_ec_typec: Update partner altmode active Abhishek Pandit-Subedi
2024-12-10 23:32 ` Stephen Boyd
2024-12-13 18:01 ` Abhishek Pandit-Subedi
2024-12-06 23:38 ` [PATCH v4 5/7] platform/chrome: cros_ec_typec: Displayport support Abhishek Pandit-Subedi
2024-12-11 0:08 ` Stephen Boyd
2024-12-13 18:29 ` Abhishek Pandit-Subedi
2024-12-16 19:46 ` Stephen Boyd
2024-12-11 21:58 ` Stephen Boyd
2024-12-13 18:33 ` Abhishek Pandit-Subedi
2024-12-16 19:49 ` Stephen Boyd
2024-12-06 23:38 ` [PATCH v4 6/7] platform/chrome: cros_ec_typec: Thunderbolt support Abhishek Pandit-Subedi
2024-12-06 23:38 ` [PATCH v4 7/7] platform/chrome: cros_ec_typec: Disable tbt on port 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=202412080010.bWqlreGq-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@google.com \
--cc=badhri@google.com \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmalani@chromium.org \
--cc=rdbabiera@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.