From: Andrew Lunn <andrew@lunn.ch>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
Tristram.Ha@microchip.com
Subject: Re: [RFC Patch net-next 4/4] net: phy: micrel: enable interrupt for ksz9477 phy
Date: Mon, 12 Sep 2022 23:33:52 +0200 [thread overview]
Message-ID: <Yx+lwApGvGnGacAa@lunn.ch> (raw)
In-Reply-To: <20220909160120.9101-5-arun.ramadoss@microchip.com>
On Fri, Sep 09, 2022 at 09:31:20PM +0530, Arun Ramadoss wrote:
> Config_intr and handle_interrupt are enabled for ksz9477 phy. It is
> similar to all other phys in the micrel phys.
>
> Signed-off-by: Arun Ramadoss <arun.ramadoss@microchip.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2022-09-12 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 16:01 [RFC Patch net-next 0/4] net: dsa: microchip: ksz9477: enable interrupt for internal phy link detection Arun Ramadoss
2022-09-09 16:01 ` [RFC Patch net-next 1/4] net: dsa: microchip: determine number of port irq based on switch type Arun Ramadoss
2022-09-12 21:22 ` Andrew Lunn
2022-09-09 16:01 ` [RFC Patch net-next 2/4] net: dsa: microchip: enable phy interrupts only if interrupt enabled in dts Arun Ramadoss
2022-09-12 21:30 ` Andrew Lunn
2022-09-09 16:01 ` [RFC Patch net-next 3/4] net: dsa: microchip: move interrupt handling logic from lan937x to ksz_common Arun Ramadoss
2022-09-09 16:01 ` [RFC Patch net-next 4/4] net: phy: micrel: enable interrupt for ksz9477 phy Arun Ramadoss
2022-09-12 21:33 ` Andrew Lunn [this message]
2022-09-12 21:33 ` [RFC Patch net-next 0/4] net: dsa: microchip: ksz9477: enable interrupt for internal phy link detection Andrew Lunn
2022-09-13 4:21 ` Arun.Ramadoss
2022-09-13 12:18 ` 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=Yx+lwApGvGnGacAa@lunn.ch \
--to=andrew@lunn.ch \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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®