public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: kernel test robot <lkp@intel.com>, <linux-usb@vger.kernel.org>,
	<palmer@dabbelt.com>
Subject: Re: [usb:usb-next] BUILD SUCCESS WITH WARNING df49f2a0ac4a34c0cb4b5c233fcfa0add644c43c
Date: Fri, 16 Jun 2023 08:49:09 +0100	[thread overview]
Message-ID: <20230616-unnerving-surface-a78ff2c38a18@wendy> (raw)
In-Reply-To: <2023061617-unnoticed-snugly-a110@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

On Fri, Jun 16, 2023 at 08:14:05AM +0200, Greg Kroah-Hartman wrote:
> 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.

I dunno if it has anything to do with the LKP folks, my copes of gcc-11.3,
gcc-12.2 & gcc-13.1 complain in a similar way on riscv.

Palmer, any clue?

USB_STRAP_HOST is `#define USB_STRAP_HOST BIT(17)` and cdn3s() doesn't
seem to even exist?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-06-16  7:49 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
2023-06-16  7:49   ` Conor Dooley [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=20230616-unnerving-surface-a78ff2c38a18@wendy \
    --to=conor.dooley@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=palmer@dabbelt.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