netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Moritz Fischer <mdf@kernel.org>, netdev@vger.kernel.org
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
	linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] net: fixed_phy: Add forward declaration for struct gpio_desc;
Date: Tue, 3 Sep 2019 12:46:01 -0700	[thread overview]
Message-ID: <9183ccfe-ab3d-3935-58e9-9475ed411604@gmail.com> (raw)
In-Reply-To: <20190903184652.3148-1-mdf@kernel.org>

On 9/3/19 11:46 AM, Moritz Fischer wrote:
> Add forward declaration for struct gpio_desc in order to address
> the following:
> 
> ./include/linux/phy_fixed.h:48:17: error: 'struct gpio_desc' declared inside parameter list [-Werror]
> ./include/linux/phy_fixed.h:48:17: error: its scope is only this definition or declaration, which is probably not what you want [-Werror]
> 
> Fixes commit 71bd106d2567 ("net: fixed-phy: Add
> fixed_phy_register_with_gpiod() API")

There is a standardized tag for that which is:

Fixes: 71bd106d2567 ("net: fixed-phy: Add
fixed_phy_register_with_gpiod() API")

Other than that:

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>

> Signed-off-by: Moritz Fischer <mdf@kernel.org>
> ---
>  include/linux/phy_fixed.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/linux/phy_fixed.h b/include/linux/phy_fixed.h
> index 1e5d86ebdaeb..52bc8e487ef7 100644
> --- a/include/linux/phy_fixed.h
> +++ b/include/linux/phy_fixed.h
> @@ -11,6 +11,7 @@ struct fixed_phy_status {
>  };
>  
>  struct device_node;
> +struct gpio_desc;
>  
>  #if IS_ENABLED(CONFIG_FIXED_PHY)
>  extern int fixed_phy_change_carrier(struct net_device *dev, bool new_carrier);
> 


-- 
Florian

  reply	other threads:[~2019-09-03 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 18:46 [PATCH] net: fixed_phy: Add forward declaration for struct gpio_desc; Moritz Fischer
2019-09-03 19:46 ` Florian Fainelli [this message]
2019-09-05  9:54 ` David Miller

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=9183ccfe-ab3d-3935-58e9-9475ed411604@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).