From: Richard Cochran <richardcochran@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Divya.Koppera@microchip.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v5 net-next 2/2] net: phy: micrel: Fix warn: passing zero to PTR_ERR
Date: Tue, 6 Dec 2022 08:39:42 -0800 [thread overview]
Message-ID: <Y49wTlpRyYsweM7u@hoboy.vegasvil.org> (raw)
In-Reply-To: <Y49M++waEHLm0hEA@lunn.ch>
On Tue, Dec 06, 2022 at 03:08:59PM +0100, Andrew Lunn wrote:
> > > > - if (!IS_ENABLED(CONFIG_PTP_1588_CLOCK) ||
> > > > - !IS_ENABLED(CONFIG_NETWORK_PHY_TIMESTAMPING))
> > > > - return 0;
> > > > -
> > >
> > > Why are you removing this ?
> > >
> >
> > I got review comment from Richard in v2 as below, making it as consistent by checking ptp_clock. So removed it in next revision.
> >
> > " > static int lan8814_ptp_probe_once(struct phy_device *phydev)
> > > {
> > > struct lan8814_shared_priv *shared = phydev->shared->priv;
> > >
> > > if (!IS_ENABLED(CONFIG_PTP_1588_CLOCK) ||
> > > !IS_ENABLED(CONFIG_NETWORK_PHY_TIMESTAMPING))
> > > return 0;
> >
> > It is weird to use macros here, but not before calling ptp_clock_register.
> > Make it consistent by checking shared->ptp_clock instead.
> > That is also better form."
>
> O.K. If Richard said this fine.
I just want to avoid drivers will #ifdef|IS_ENABLED all over the place.
Thanks,
Richard
next prev parent reply other threads:[~2022-12-06 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 7:35 [PATCH v5 net-next 0/2] Fixed warnings Divya Koppera
2022-12-06 7:35 ` [PATCH v5 net-next 1/2] net: phy: micrel: Fixed error related to uninitialized symbol ret Divya Koppera
2022-12-06 9:09 ` Jiri Pirko
2022-12-06 7:35 ` [PATCH v5 net-next 2/2] net: phy: micrel: Fix warn: passing zero to PTR_ERR Divya Koppera
2022-12-06 13:07 ` Andrew Lunn
2022-12-06 13:45 ` Divya.Koppera
2022-12-06 14:08 ` Andrew Lunn
2022-12-06 16:39 ` Richard Cochran [this message]
2022-12-12 8:34 ` Divya.Koppera
2022-12-12 10:11 ` Andrew Lunn
2022-12-13 9:55 ` Divya.Koppera
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=Y49wTlpRyYsweM7u@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=Divya.Koppera@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®