From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [usb:usb-next] BUILD SUCCESS WITH WARNING df49f2a0ac4a34c0cb4b5c233fcfa0add644c43c
Date: Fri, 16 Jun 2023 08:14:05 +0200 [thread overview]
Message-ID: <2023061617-unnoticed-snugly-a110@gregkh> (raw)
In-Reply-To: <202306160658.E79gCwiR-lkp@intel.com>
On Fri, Jun 16, 2023 at 06:12:01AM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-next
> branch HEAD: df49f2a0ac4a34c0cb4b5c233fcfa0add644c43c Revert "usb: common: usb-conn-gpio: Set last role to unknown before initial detection"
>
> Warning: (recently discovered and may have been fixed)
>
> drivers/usb/cdns3/cdns3-starfive.c:23: warning: expecting prototype for cdns3(). Prototype was for USB_STRAP_HOST() instead
I keep seeing this "warning" by the test robot for a while, but I do not
understand it at all, and can not duplicate it here locally. Are you
sure your riscv toolchain is correct as :
> Warning ids grouped by kconfigs:
>
> gcc_recent_errors
> |-- riscv-allmodconfig
> | `-- drivers-usb-cdns3-cdns3-starfive.c:warning:expecting-prototype-for-cdns3().-Prototype-was-for-USB_STRAP_HOST()-instead
> `-- riscv-allyesconfig
> `-- drivers-usb-cdns3-cdns3-starfive.c:warning:expecting-prototype-for-cdns3().-Prototype-was-for-USB_STRAP_HOST()-instead
It only seems to trigger there.
confused,
greg k-h
next prev parent reply other threads:[~2023-06-16 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 22:12 [usb:usb-next] BUILD SUCCESS WITH WARNING df49f2a0ac4a34c0cb4b5c233fcfa0add644c43c kernel test robot
2023-06-16 6:14 ` Greg Kroah-Hartman [this message]
2023-06-16 7:49 ` Conor Dooley
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=2023061617-unnoticed-snugly-a110@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@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