[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200327142245.GF11004@lunn.ch>
Date: Fri, 27 Mar 2020 15:22:45 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Florinel Iordache <florinel.iordache@....com>
Cc: davem@...emloft.net, netdev@...r.kernel.org, f.fainelli@...il.com,
hkallweit1@...il.com, linux@...linux.org.uk,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
robh+dt@...nel.org, mark.rutland@....com, kuba@...nel.org,
corbet@....net, shawnguo@...nel.org, leoyang.li@....com,
madalin.bucur@....nxp.com, ioana.ciornei@....com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 6/9] net: phy: add backplane kr driver support
> +/* Backplane custom logging */
> +#define BPDEV_LOG(name) \
> + char log_buffer[LOG_BUFFER_SIZE]; \
> + va_list args; va_start(args, msg); \
> + vsnprintf(log_buffer, LOG_BUFFER_SIZE - 1, msg, args); \
> + if (!bpphy->attached_dev) \
> + dev_##name(&bpphy->mdio.dev, log_buffer); \
> + else \
> + dev_##name(&bpphy->mdio.dev, "%s: %s", \
> + netdev_name(bpphy->attached_dev), log_buffer); \
> + va_end(args)
> +void bpdev_err(struct phy_device *bpphy, char *msg, ...)
> +{
> + BPDEV_LOG(err);
> +}
> +EXPORT_SYMBOL(bpdev_err);
> +
> +void bpdev_warn(struct phy_device *bpphy, char *msg, ...)
> +{
> + BPDEV_LOG(warn);
> +}
> +EXPORT_SYMBOL(bpdev_warn);
> +
> +void bpdev_info(struct phy_device *bpphy, char *msg, ...)
> +{
> + BPDEV_LOG(info);
> +}
> +EXPORT_SYMBOL(bpdev_info);
> +
> +void bpdev_dbg(struct phy_device *bpphy, char *msg, ...)
> +{
> + BPDEV_LOG(dbg);
> +}
> +EXPORT_SYMBOL(bpdev_dbg);
You are currently modelling this as a phydev. So please just use
phydev_err(), phydev_info(), phydev_dbg() etc.
Also, if you look at other PHY code, struct phy_device * is nearly
always called phydev. Please try to be consistent with the existing
code base.
Andrew
Powered by blists - more mailing lists