From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Leon Romanovsky <leon@kernel.org>
Cc: Peter Geis <pgwipeout@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH] net: phy: add driver for Motorcomm yt8511 phy
Date: Wed, 19 May 2021 14:15:13 +0100 [thread overview]
Message-ID: <20210519131512.GA30436@shell.armlinux.org.uk> (raw)
In-Reply-To: <YKUK8hBImIUFV35I@unreal>
On Wed, May 19, 2021 at 03:56:18PM +0300, Leon Romanovsky wrote:
> I'm sorry that I continue to ask, but is net/phy/* usable without MODULE?
Simple answer: it is.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Leon Romanovsky <leon@kernel.org>
Cc: Peter Geis <pgwipeout@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH] net: phy: add driver for Motorcomm yt8511 phy
Date: Wed, 19 May 2021 14:15:13 +0100 [thread overview]
Message-ID: <20210519131512.GA30436@shell.armlinux.org.uk> (raw)
In-Reply-To: <YKUK8hBImIUFV35I@unreal>
On Wed, May 19, 2021 at 03:56:18PM +0300, Leon Romanovsky wrote:
> I'm sorry that I continue to ask, but is net/phy/* usable without MODULE?
Simple answer: it is.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-05-19 13:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 21:46 [PATCH] net: phy: add driver for Motorcomm yt8511 phy Peter Geis
2021-05-11 21:46 ` Peter Geis
2021-05-11 21:56 ` Russell King - ARM Linux admin
2021-05-11 21:56 ` Russell King - ARM Linux admin
2021-05-11 22:56 ` Peter Geis
2021-05-11 22:56 ` Peter Geis
2021-05-18 8:59 ` Leon Romanovsky
2021-05-18 8:59 ` Leon Romanovsky
2021-05-19 0:20 ` Peter Geis
2021-05-19 0:20 ` Peter Geis
2021-05-19 8:18 ` Leon Romanovsky
2021-05-19 8:18 ` Leon Romanovsky
2021-05-19 10:37 ` Heiner Kallweit
2021-05-19 10:37 ` Heiner Kallweit
2021-05-19 11:50 ` Leon Romanovsky
2021-05-19 11:50 ` Leon Romanovsky
2021-05-19 12:45 ` Peter Geis
2021-05-19 12:45 ` Peter Geis
2021-05-19 12:56 ` Leon Romanovsky
2021-05-19 12:56 ` Leon Romanovsky
2021-05-19 13:15 ` Russell King (Oracle) [this message]
2021-05-19 13:15 ` Russell King (Oracle)
2021-05-19 13:25 ` Peter Geis
2021-05-19 13:25 ` Peter Geis
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=20210519131512.GA30436@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=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pgwipeout@gmail.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.