From: David Miller <davem@davemloft.net>
To: Woojung.Huh@microchip.com
Cc: f.fainelli@gmail.com, andrew@lunn.ch, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] phy: add phy fixup unregister functions
Date: Tue, 06 Dec 2016 10:01:04 -0500 (EST) [thread overview]
Message-ID: <20161206.100104.1134856835372946560.davem@davemloft.net> (raw)
In-Reply-To: <9235D6609DB808459E95D78E17F2E43D40975526@CHN-SV-EXMX02.mchp-main.com>
From: <Woojung.Huh@microchip.com>
Date: Fri, 2 Dec 2016 23:04:13 +0000
> From: Woojung Huh <woojung.huh@microchip.com>
>
> Add functions to unregister phy fixup for modules.
>
> phy_unregister_fixup(const char *bus_id, u32 phy_uid, u32 phy_uid_mask)
> Unregister phy fixup matches bus_id, phy_uid and phy_uid_mask
> from phy_fixup_list.
> Return 0 when find matched one and remove from the list.
> Return -ENODEV when fail to find it on the list.
>
> phy_unregister_fixup_for_uid(u32 phy_uid, u32 phy_uid_mask)
> Unregister phy fixup from phy_fixup_list.
> Use it for fixup registered by phy_register_fixup_for_uid()
> Return 0 when find matched one and remove from the list.
> Return -ENODEV when fail to find it on the list.
>
> phy_unregister_fixup_for_id(const char *bus_id)
> Unregister phy fixup from phy_fixup_list.
> Use it for fixup registered by phy_register_fixup_for_id()
> Return 0 when find matched one and remove from the list.
> Return -ENODEV when fail to find it on the list.
>
> Signed-off-by: Woojung Huh <woojung.huh@microchip.com>
Please submit this along with whatever will be the first user(s) of these
new interfaces.
next prev parent reply other threads:[~2016-12-06 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 23:04 [PATCH net-next] phy: add phy fixup unregister functions Woojung.Huh
2016-12-06 15:01 ` David Miller [this message]
2016-12-06 15:44 ` Woojung.Huh
2016-12-06 15:56 ` David Miller
2016-12-06 15:57 ` Woojung.Huh
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=20161206.100104.1134856835372946560.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--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