From: "Russell King (Oracle)" <linux@armlinux.org.uk> To: Michal Simek <michal.simek@xilinx.com>, Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com> Cc: Andrew Lunn <andrew@lunn.ch>, Heiner Kallweit <hkallweit1@gmail.com>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org Subject: [PATCH net-next 0/3] net: xilinx: phylink validate implementation updates Date: Tue, 16 Nov 2021 09:54:59 +0000 [thread overview] Message-ID: <YZN/86huhkUGzZuV@shell.armlinux.org.uk> (raw) Hi, This series converts axienet to fill in the supported_interfaces member of phylink_config, cleans up the validate() implementation, and then converts to phylink_generic_validate(). drivers/net/ethernet/xilinx/xilinx_axienet_main.c | 71 ++++------------------- 1 file changed, 11 insertions(+), 60 deletions(-) -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk> To: Michal Simek <michal.simek@xilinx.com>, Radhey Shyam Pandey <radhey.shyam.pandey@xilinx.com> Cc: Andrew Lunn <andrew@lunn.ch>, Heiner Kallweit <hkallweit1@gmail.com>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org Subject: [PATCH net-next 0/3] net: xilinx: phylink validate implementation updates Date: Tue, 16 Nov 2021 09:54:59 +0000 [thread overview] Message-ID: <YZN/86huhkUGzZuV@shell.armlinux.org.uk> (raw) Hi, This series converts axienet to fill in the supported_interfaces member of phylink_config, cleans up the validate() implementation, and then converts to phylink_generic_validate(). drivers/net/ethernet/xilinx/xilinx_axienet_main.c | 71 ++++------------------- 1 file changed, 11 insertions(+), 60 deletions(-) -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-11-16 9:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-16 9:54 Russell King (Oracle) [this message] 2021-11-16 9:54 ` [PATCH net-next 0/3] net: xilinx: phylink validate implementation updates Russell King (Oracle) 2021-11-16 9:55 ` [PATCH net-next 1/3] net: axienet: populate supported_interfaces member Russell King (Oracle) 2021-11-16 9:55 ` Russell King (Oracle) 2021-11-16 9:55 ` [PATCH net-next 2/3] net: axienet: remove interface checks in axienet_validate() Russell King (Oracle) 2021-11-16 9:55 ` Russell King (Oracle) 2021-11-16 9:55 ` [PATCH net-next 3/3] net: axienet: use phylink_generic_validate() Russell King (Oracle) 2021-11-16 9:55 ` Russell King (Oracle) 2021-11-16 11:12 ` [PATCH net-next 0/3] net: xilinx: phylink validate implementation updates Michal Simek 2021-11-16 11:12 ` Michal Simek 2021-11-17 11:30 ` patchwork-bot+netdevbpf 2021-11-17 11:30 ` patchwork-bot+netdevbpf
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=YZN/86huhkUGzZuV@shell.armlinux.org.uk \ --to=linux@armlinux.org.uk \ --cc=andrew@lunn.ch \ --cc=davem@davemloft.net \ --cc=hkallweit1@gmail.com \ --cc=kuba@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=michal.simek@xilinx.com \ --cc=netdev@vger.kernel.org \ --cc=radhey.shyam.pandey@xilinx.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: linkBe 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.