From: Andrew Lunn <andrew@lunn.ch>
To: Liang Xu <lxu@maxlinear.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"vee.khee.wong@linux.intel.com" <vee.khee.wong@linux.intel.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
Hauke Mehrtens <hmehrtens@maxlinear.com>,
Thomas Mohren <tmohren@maxlinear.com>
Subject: Re: [PATCH v3] net: phy: add Maxlinear GPY115/21x/24x driver
Date: Sat, 5 Jun 2021 16:51:17 +0200 [thread overview]
Message-ID: <YLuPZTXFrJ9KjNpl@lunn.ch> (raw)
In-Reply-To: <2b9945f9-16a4-bda5-40df-d79089be3c12@maxlinear.com>
> >>> This does not access vendor specific registers, should not this be part
> >>> of the standard genphy_read_abilities() or moved to a helper?
> >>>
> >> genphy_read_abilities does not cover 2.5G.
> >>
> >> genphy_c45_pma_read_abilities checks C45 ids and this check fail if
> >> is_c45 is not set.
> > You appear to of ignored my comment about this. Please add the helper
> > to the core as i suggested, and then use
> > genphy_c45_pma_read_abilities().
> >
> > Andrew
> >
> I'm new to upstream and do not know the process to change code in core.
Pretty much the same way you change code in a driver. Submit a path!
Please put it into a separate patch, so making a patch series. Please
add some kernel doc style documentation, describing what the function
does. Look at other functions in phy_device.c for examples.
Anybody can change core code. It just gets looked at closer, and need
to be generic.
Andrew
next prev parent reply other threads:[~2021-06-05 14:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:12 [PATCH v3] net: phy: add Maxlinear GPY115/21x/24x driver Xu Liang
2021-06-04 16:24 ` Florian Fainelli
2021-06-04 18:24 ` Liang Xu
2021-06-04 20:10 ` Andrew Lunn
2021-06-05 3:35 ` Liang Xu
2021-06-05 14:51 ` Andrew Lunn [this message]
2021-06-07 4:06 ` Liang Xu
2021-06-18 9:17 ` Liang Xu
2021-06-18 14:01 ` Andrew Lunn
2021-06-18 15:36 ` Liang Xu
2021-06-21 2:30 ` Andrew Lunn
2021-06-21 5:05 ` Liang Xu
2021-06-21 12:48 ` Andrew Lunn
2021-06-21 13:07 ` Liang Xu
2021-06-04 18:37 ` Liang Xu
2021-06-04 19:44 ` Martin Blumenstingl
2021-06-05 3:32 ` Liang Xu
2021-06-05 17:24 ` Andrew Lunn
2021-06-07 4:37 ` Liang Xu
2021-06-07 20:28 ` Martin Blumenstingl
[not found] ` <MWHPR19MB0077D01E4EAFA9FE521D83ECBD0D9@MWHPR19MB0077.namprd19.prod.outlook.com>
[not found] ` <766ab274-25ff-c9a2-1ed6-fe2aa44b4660@maxlinear.com>
2021-06-23 21:09 ` Martin Blumenstingl
2021-06-24 1:06 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 4:21 Ismail, Mohammad Athari
2021-06-22 13:16 ` Andrew Lunn
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=YLuPZTXFrJ9KjNpl@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=hmehrtens@maxlinear.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--cc=tmohren@maxlinear.com \
--cc=vee.khee.wong@linux.intel.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;
as well as URLs for NNTP newsgroup(s).