From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Prashant Malani <pmalani@chromium.org>,
Uday Bhat <uday.m.bhat@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
oe-kbuild-all@lists.linux.dev, Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Emilie Roberts <hadrosaur@google.com>,
"Nyman, Mathias" <mathias.nyman@intel.com>,
"Regupathy, Rajaram" <rajaram.regupathy@intel.com>,
"Radjacoumar, Shyam Sundar" <ssradjacoumar@google.com>,
Samuel Jacob <samjaco@google.com>,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] platform/chrome: cros_ec_typec: Make sure the USB role switch has PLD
Date: Thu, 8 Feb 2024 11:12:56 +0200 [thread overview]
Message-ID: <ZcSbGIBt1BtFQd36@kuha.fi.intel.com> (raw)
In-Reply-To: <202402081136.sve0cViZ-lkp@intel.com>
On Thu, Feb 08, 2024 at 12:07:40PM +0800, kernel test robot wrote:
> Hi Heikki,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on usb/usb-testing]
> [also build test ERROR on usb/usb-next usb/usb-linus chrome-platform/for-next chrome-platform/for-firmware-next driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus linus/master v6.8-rc3 next-20240207]
> [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/Heikki-Krogerus/usb-roles-Link-the-switch-to-its-connector/20240207-230017
> base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> patch link: https://lore.kernel.org/r/20240207145851.1603237-3-heikki.krogerus%40linux.intel.com
> patch subject: [PATCH 2/2] platform/chrome: cros_ec_typec: Make sure the USB role switch has PLD
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240208/202402081136.sve0cViZ-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240208/202402081136.sve0cViZ-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/202402081136.sve0cViZ-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> drivers/platform/chrome/cros_ec_typec.c: In function 'cros_typec_parse_port_props':
> >> drivers/platform/chrome/cros_ec_typec.c:75:34: error: invalid use of undefined type 'struct acpi_device'
> 75 | if (adev && !adev->pld_crc)
> | ^~
> drivers/platform/chrome/cros_ec_typec.c:76:29: error: invalid use of undefined type 'struct acpi_device'
> 76 | adev->pld_crc = to_acpi_device_node(fwnode)->pld_crc;
> | ^~
> drivers/platform/chrome/cros_ec_typec.c:76:68: error: invalid use of undefined type 'struct acpi_device'
> 76 | adev->pld_crc = to_acpi_device_node(fwnode)->pld_crc;
> | ^~
Oh, so this has to be wrapped in ifdef CONFIG_ACPI :(
--
heikki
next prev parent reply other threads:[~2024-02-08 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 14:58 [PATCH 0/2] platform/chrome: typec: xHCI DbC Heikki Krogerus
2024-02-07 14:58 ` [PATCH 1/2] usb: roles: Link the switch to its connector Heikki Krogerus
2024-02-07 14:58 ` [PATCH 2/2] platform/chrome: cros_ec_typec: Make sure the USB role switch has PLD Heikki Krogerus
2024-02-07 19:14 ` Sergei Shtylyov
2024-02-07 22:52 ` kernel test robot
2024-02-08 4:07 ` kernel test robot
2024-02-08 9:12 ` Heikki Krogerus [this message]
2024-02-08 18:14 ` 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=ZcSbGIBt1BtFQd36@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=hadrosaur@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmalani@chromium.org \
--cc=rajaram.regupathy@intel.com \
--cc=samjaco@google.com \
--cc=ssradjacoumar@google.com \
--cc=tzungbi@kernel.org \
--cc=uday.m.bhat@intel.com \
/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).