On Fri, Jun 04, 2021 at 11:07:42AM -0400, Konstantin Ryabitsev wrote:
> > 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.
This is now in place -- lore will now prefer results from DKIM-friendly
sources. E.g. grabbing the same message-id will now return the thread from
linux-usb (via vger) instead of linux-amlogic (via infradead).
$ b4 am -o/tmp 20210601084830.260196-1-narmstrong@xxxxxxxxxxxx
Looking up https://lore.kernel.org/r/20210601084830.260196-1-narmstrong%40baylibre.com
Grabbing thread from lore.kernel.org/linux-usb/20210601084830.260196-1-narmstrong%40baylibre.com/t.mbox.gz
Analyzing 4 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@xxxxxxxxxxxxxx> (✓ DKIM/googlemail.com)
---
✓ Signed: openpgp/narmstrong@xxxxxxxxxxxx
✓ Signed: DKIM/baylibre-com.20150623.gappssmtp.com (From: narmstrong@xxxxxxxxxxxx)
---
Total patches: 1
---
Link: https://lore.kernel.org/r/20210601084830.260196-1-narmstrong@xxxxxxxxxxxx
Base: not found
git am /tmp/20210601_narmstrong_usb_dwc3_meson_g12a_fix_usb2_phy_glue_init_when_phy0_is_disabled.mbx
-K
