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: <a843cb62-ea72-74b6-589b-9db98477f169@gmail.com>
Date:   Thu, 10 Nov 2022 10:16:39 -0800
From:   Florian Fainelli <f.fainelli@...il.com>
To:     maxime@...no.tech, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Ray Jui <rjui@...adcom.com>,
        Scott Branden <sbranden@...adcom.com>,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@...adcom.com>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     linux-rpi-kernel@...ts.infradead.org,
        Dave Stevenson <dave.stevenson@...pberrypi.com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Phil Elwell <phil@...pberrypi.com>,
        linux-kernel@...r.kernel.org, Dom Cobley <dom@...pberrypi.com>
Subject: Re: [PATCH 0/2] ARM: dts: bcm283x: Switch to firmware clocks for
 Pi0-3

On 10/26/22 06:17, maxime@...no.tech wrote:
> Hi,
> 
> Over the years, the differences between the Pi0-3 and the Pi4 created a bunch
> of issues in the KMS driver that trace back to the policy differences between
> the clk-bcm2835 and clk-raspberrypi drivers.
> 
> Instead of piling hacks over hacks to work around those differences, let's just
> follow what downstream is doing and use the clk-raspberrypi for all the KMS
> related devices.
> 
> Let me know what you think,

Maxime, please fix your git configuration such that the author of the 
patches is:

Maxime Ripard <maxime@...no.tech>

and not:

maxime@...no.tech

which git am then translates into maxime@...no.tech <maxime@...no.tech>

causing the email vs. author checks to fail on my end (and then in 
linux-next).

Thanks!
-- 
Florian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ