Netdev List
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, hkallweit1@gmail.com,
	linux@armlinux.org.uk, netdev@vger.kernel.org,
	UNGLinuxDriver@microchip.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] net: ethernet: oa_tc6: deliver the PHY interrupt to phylib
Date: Fri, 4 Sep 2026 15:07:31 +0200	[thread overview]
Message-ID: <844a369e-3e52-4489-b8b1-d359789bfcb3@lunn.ch> (raw)
In-Reply-To: <a01b3780-b36d-4544-a372-9daa3be20a9f@microchip.com>

> +     /* Populate all irq[] entries before registration so
> +      * phy_device_create() picks up the virtual IRQ regardless of
> +      * the PHY's MDIO address.
> +      */
> +     for (i = 0; i < PHY_MAX_ADDR; i++)
> +             tc6->mdiobus->irq[i] = tc6->phy_virq;

Yes, or just a memcpy().

     Andrew

  reply	other threads:[~2026-09-04 13:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 13:09 [PATCH net-next 0/3] net: microchip_t1s: fix collision detection on PLCA status change Parthiban Veerasooran
2026-09-01 13:09 ` [PATCH net-next 1/3] net: phy: " Parthiban Veerasooran
2026-09-01 13:09 ` [PATCH net-next 2/3] net: ethernet: oa_tc6: deliver the PHY interrupt to phylib Parthiban Veerasooran
2026-09-02  0:30   ` Andrew Lunn
2026-09-03 13:23     ` Parthiban Veerasooran
2026-09-03 14:14       ` Andrew Lunn
2026-09-04  6:05         ` Parthiban Veerasooran
2026-09-04 13:07           ` Andrew Lunn [this message]
2026-09-02  0:43   ` Andrew Lunn
2026-09-03 13:02     ` Parthiban Veerasooran
2026-09-03 13:54       ` Andrew Lunn
2026-09-04  6:02         ` Parthiban Veerasooran
2026-09-01 13:09 ` [PATCH net-next 3/3] net: phy: microchip_t1s: fix collision detection for LAN867X Rev.D0 Parthiban Veerasooran

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=844a369e-3e52-4489-b8b1-d359789bfcb3@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@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 \
    --cc=parthiban.veerasooran@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