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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 11 Jun 2021 13:08:43 +0100
From:   "Russell King (Oracle)" <>
To:     "Rafael J. Wysocki" <>
Cc:     Andy Shevchenko <>,
        Ioana Ciornei <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        Heiner Kallweit <>,
        netdev <>,
        Grant Likely <>,
        Jeremy Linton <>,
        Andrew Lunn <>,
        Florian Fainelli <>,
        Heikki Krogerus <>,
        Marcin Wojtas <>,
        Pieter Jansen Van Vuuren <>,
        Jon <>, Saravana Kannan <>,
        Randy Dunlap <>,
        Calvin Johnson <>,
        Cristi Sovaiala <>,
        Florin Laurentiu Chiculita <>,
        Madalin Bucur <>,
        linux-arm Mailing List <>,
        Diana Madalina Craciun <>,
        ACPI Devel Maling List <>,
        Linux Kernel Mailing List <>,
        "linux.cj" <>,
        Laurentiu Tudor <>,
        Len Brown <>,
        "Rafael J . Wysocki" <>,
        Ioana Ciornei <>
Subject: Re: [PATCH net-next v9 03/15] net: phy: Introduce phy related fwnode

On Fri, Jun 11, 2021 at 01:40:59PM +0200, Rafael J. Wysocki wrote:
> I'm not sure why you want the above to be two if () statements instead of one?
> I would change the ordering anyway, that is
> if (!IS_ERR(phy_node) || is_acpi_node(fwnode))
>         return phy_node;
> And I think that the is_acpi_node() check is there to return the error
> code right away so as to avoid returning a "not found" error later.
> But I'm not sure if this is really necessary.  Namely, if nothing
> depends on the specific error code returned by this function, it would
> be somewhat cleaner to let the code below run if phy_node is an error
> pointer in the ACPI case, because in that case the code below will
> produce an error pointer anyway.

However, that opens the door to someone shipping "working" ACPI with
one of these names that we've taken the decision not to support on
ACPI firmware. Surely, it's much better that we don't accept the
legacy names so we don't allow such configurations to work.

RMK's Patch system:
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

Powered by blists - more mailing lists