From: Jakub Kicinski <kuba@kernel.org>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <olteanv@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<linux@armlinux.org.uk>, <Tristram.Ha@microchip.com>,
<prasanna.vengateshan@microchip.com>, <hkallweit1@gmail.com>
Subject: Re: [Patch net-next v3 2/6] net: dsa: microchip: enable phy interrupts only if interrupt enabled in dts
Date: Wed, 21 Sep 2022 18:11:16 -0700 [thread overview]
Message-ID: <20220921181116.58b1163a@kernel.org> (raw)
In-Reply-To: <20220916091348.8570-3-arun.ramadoss@microchip.com>
On Fri, 16 Sep 2022 14:43:44 +0530 Arun Ramadoss wrote:
> + if (dev->irq > 0) {
> + ret = lan937x_irq_phy_setup(dev);
> + if (ret)
> + return ret;
This no longer applies cleanly after 2f8a786f472445
please rebase & repost.
next prev parent reply other threads:[~2022-09-22 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 9:13 [Patch net-next v3 0/6] net: dsa: microchip: ksz9477: enable interrupt for internal phy link detection Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 1/6] net: dsa: microchip: determine number of port irq based on switch type Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 2/6] net: dsa: microchip: enable phy interrupts only if interrupt enabled in dts Arun Ramadoss
2022-09-22 1:11 ` Jakub Kicinski [this message]
2022-09-16 9:13 ` [Patch net-next v3 3/6] net: dsa: microchip: lan937x: return zero if mdio node not present Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 4/6] net: dsa: microchip: move interrupt handling logic from lan937x to ksz_common Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 5/6] net: dsa: microchip: use common irq routines for girq and pirq Arun Ramadoss
2022-09-16 9:13 ` [Patch net-next v3 6/6] net: phy: micrel: enable interrupt for ksz9477 phy Arun Ramadoss
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=20220921181116.58b1163a@kernel.org \
--to=kuba@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--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=prasanna.vengateshan@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.