Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 4 Jun 2021 11:07:42 -0400
From:   Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Neil Armstrong <narmstrong@baylibre.com>, balbi@kernel.org,
        linux-usb@vger.kernel.org, linux-amlogic@lists.infradead.org,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3-meson-g12a: fix usb2 PHY glue init when phy0
 is disabled
Message-ID: <20210604150742.bssvnhm4gv72uw4h@nitro.local>
References: <20210601084830.260196-1-narmstrong@baylibre.com>
 <YLoHSJIOSRTyF0r1@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <YLoHSJIOSRTyF0r1@kroah.com>
Precedence: bulk

On Fri, Jun 04, 2021 at 12:58:16PM +0200, Greg KH wrote:
> Meta comment, you signed this, and it worked!

NOICE. \o/

> Looking up https://lore.kernel.org/r/20210601084830.260196-1-narmstrong%40baylibre.com
> Grabbing thread from lore.kernel.org/linux-amlogic/20210601084830.260196-1-narmstrong%40baylibre.com/t.mbox.gz
> Analyzing 2 messages in the thread
> Checking attestation on all messages, may take a moment...
> ---
>   ✓ [PATCH] usb: dwc3-meson-g12a: fix usb2 PHY glue init when phy0 is disabled
>     + Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> (✓ DKIM/lists.infradead.org)
>   ---
>   ✓ Signed: openpgp/narmstrong@baylibre.com
>   ✗ BADSIG: DKIM/baylibre-com.20150623.gappssmtp.com
>   ✓ Signed: DKIM/lists.infradead.org (From: narmstrong@baylibre.com)
> ---
> Total patches: 1
> ---
>  Link: https://lore.kernel.org/r/20210601084830.260196-1-narmstrong@baylibre.com
>  Base: not found
> Applying: usb: dwc3-meson-g12a: fix usb2 PHY glue init when phy0 is disabled
> 
> 
> Odd that DKIM didn't work for baylibre-com, but hey, I'll take a real
> signature over DKIM anyday!

That lookup happened to grab the thread from linux-amlogic, which is
mailman2-managed and is known to break DKIM. I'll try to fix our configuration
so that known-DKIM-friendly sources are given priority. This way, when a thread
exists on multiple lists, you'll get the one more likely to pass DKIM checks.

> thanks for doing this.

Yes, thanks! Hopefully, more people will start doing this.

-K