lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAOesGMi+ymn_FdDfgTjwgyO-MsEJNGBDU9ayRJvGkjJ7T_ExfA@mail.gmail.com> Date: Tue, 26 Jan 2016 10:14:00 -0800 From: Olof Johansson <olof@...om.net> To: Andrew Lunn <andrew@...n.ch> Cc: Aaro Koskinen <aaro.koskinen@...ia.com>, Florian Fainelli <f.fainelli@...il.com>, "David S. Miller" <davem@...emloft.net>, Network Development <netdev@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org> Subject: Re: [BISECTED] v4.5-rc1 phylib regression +devicetree@...r.kernel.org instead. On Tue, Jan 26, 2016 at 10:08 AM, Olof Johansson <olof@...om.net> wrote: > On Tue, Jan 26, 2016 at 9:53 AM, Andrew Lunn <andrew@...n.ch> wrote: >>> I hate to bikeshed, but I'm not sure if "generic-mdio" is too... >>> generic? Will someone writing a DT be thinking "well, this is a >>> generic mdio PHY, I should set it"? "mdio-device"? >>> "generic-nonphy-mdio"? Neither of those seem much better. >> >> How about 'not-a-phy'? > > "mdio,not-a-phy" or "mdio,non-phy" will scope it a bit, especially if > you expect other generic mdio properties that can do with a namespace. > > Probably time to add devicetree-discuss. Doing so. > > > -Olof
Powered by blists - more mailing lists