LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Ebner <manuelebner@mailbox.org>
To: Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-next@vger.kernel.org, linux-usb@vger.kernel.org,
	 linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	 stable@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] USB: phy: fsl-usb: fix missing static keywords
Date: Sat, 18 Jul 2026 13:30:11 +0200	[thread overview]
Message-ID: <49ad090f48d0ad38a46642c2ddd019ae3cfebc82.camel@mailbox.org> (raw)
In-Reply-To: <20260717154957.1853976-1-johan@kernel.org>

On Fri, 2026-07-17 at 17:49 +0200, Johan Hovold wrote:
> A recent change enabling compile testing of a Freescale dual-role
> controller indirectly enabled a USB PHY driver to be built. That driver
> in turn is missing a bunch of static keywords which results in warnings
> like:
> 
> drivers/usb/phy/phy-fsl-usb.c:105:5: error: no previous prototype for 'write_ulpi' [-
> Werror=missing-prototypes]
>   105 | int write_ulpi(u8 addr, u8 data)
>         |     ^~~~~~~~~~
> 
> which consequently breaks -Werror builds.
> 
> Add the missing static keywords.
> 
> Fixes: 0807c500a1a6 ("USB: add Freescale USB OTG Transceiver driver")
> Cc: stable@vger.kernel.org	# 3.0

Add linux-next@vger.kernel.org

> Reported-by: Mark Brown <broonie@kernel.org>
> Link: https://lore.kernel.org/r/4f9f5ff9-8eaa-4bd5-9331-37119f78e13f@sirena.org.uk
> Signed-off-by: Johan Hovold <johan@kernel.org>

Reviewed-by: Manuel Ebner <manuelebner@mailbox.org>

Thanks
 Manuel

> ---
>  drivers/usb/phy/phy-fsl-usb.c | 52 +++++++++++++++++------------------
>  drivers/usb/phy/phy-fsl-usb.h |  6 ++--
>  2 files changed, 29 insertions(+), 29 deletions(-)
> 
> [...]


      reply	other threads:[~2026-07-18 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 15:49 [PATCH] USB: phy: fsl-usb: fix missing static keywords Johan Hovold
2026-07-18 11:30 ` Manuel Ebner [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=49ad090f48d0ad38a46642c2ddd019ae3cfebc82.camel@mailbox.org \
    --to=manuelebner@mailbox.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox