From: Marek Vasut <marex@nabladev.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: drivers/usb/dwc3/dwc3-generic-plat.c:114:35: error: implicit declaration of function 'FIELD_PREP'
Date: Mon, 31 Aug 2026 05:12:07 +0200 [thread overview]
Message-ID: <bbfe7f10-3c96-4516-9576-276f69be8e96@nabladev.com> (raw)
In-Reply-To: <202608310438.95i46Myq-lkp@intel.com>
On 8/31/26 4:39 AM, kernel test robot wrote:
> tree: https://github.com/intel-lab-lkp/linux/commits/Marek-Vasut/dt-bindings-phy-Document-ST-STM32MP25-USB2-FEMTO-PHY/20260822-094634
> head: 37913ed44bd5c9e2fe5e7bd8ea4188171e6740b7
> commit: baaedb19717a9c195ea1823e134a40ac6ca68036 usb: dwc3: dwc3-generic-plat: Add ST STM32MP2 DWC3 xHCI USB controller glue
> date: 8 days ago
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260831/202608310438.95i46Myq-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 16.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260831/202608310438.95i46Myq-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/202608310438.95i46Myq-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> drivers/usb/dwc3/dwc3-generic-plat.c: In function 'dwc3_stm32mp25_init':
>>> drivers/usb/dwc3/dwc3-generic-plat.c:114:35: error: implicit declaration of function 'FIELD_PREP' [-Wimplicit-function-declaration]
> 114 | FIELD_PREP(STM32MP2_USB3DRCR_HOST_PORT_POWER_CONTROL_PRESENT,
> | ^~~~~~~~~~
>
This should be already fixed in V4.
prev parent reply other threads:[~2026-08-31 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 2:39 drivers/usb/dwc3/dwc3-generic-plat.c:114:35: error: implicit declaration of function 'FIELD_PREP' kernel test robot
2026-08-31 3:12 ` Marek Vasut [this message]
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=bbfe7f10-3c96-4516-9576-276f69be8e96@nabladev.com \
--to=marex@nabladev.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.