linux-kernel - Re: [PATCH 1/3] serial: 8250: of: Check for CONFIG_SERIAL_8250

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <X79nh3UUzZfH17Qs@kroah.com>
Date:   Thu, 26 Nov 2020 09:29:59 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Al Cooper <alcooperx@...il.com>
Cc:     linux-kernel@...r.kernel.org, Jim Quinlan <jquinlan@...adcom.com>,
        bcm-kernel-feedback-list@...adcom.com, devicetree@...r.kernel.org,
        Jiri Slaby <jirislaby@...nel.org>,
        linux-serial@...r.kernel.org, linux-usb@...r.kernel.org,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 1/3] serial: 8250: of: Check for
 CONFIG_SERIAL_8250_BCM7271

On Fri, Nov 20, 2020 at 02:43:03PM -0500, Al Cooper wrote:
> From: Jim Quinlan <jquinlan@...adcom.com>
> 
> This commit has of_platform_serial_probe() check specifically for the
> "brcm,bcm7271-uart" and whether its companion driver is enabled. If it
> is the case, and the clock provider is not ready, we want to make sure
> that when the 8250_bcm7271.c driver returns EPROBE_DEFER, we are not
> getting the UART registered via 8250_of.c.
> 
> Signed-off-by: Jim Quinlan <jquinlan@...adcom.com>
> ---

When forwarding on patches from others, always include your
signed-off-by: as well, to ensure that you have reviewed this and are ok
with it.  I can't take this as-is, sorry.

And why did you include linux-usb@...r for this patch series?

thanks,

greg k-h