linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@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
Date: Sat, 5 Jun 2021 09:02:50 +0200	[thread overview]
Message-ID: <YLshmr+H4mES+kZX@kroah.com> (raw)
In-Reply-To: <20210604164601.hrlgkrsghhqtho6m@nitro.local>

On Fri, Jun 04, 2021 at 12:46:01PM -0400, Konstantin Ryabitsev wrote:
> 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@baylibre.com
>     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@googlemail.com> (✓ DKIM/googlemail.com)
>       ---
>       ✓ Signed: openpgp/narmstrong@baylibre.com
>       ✓ Signed: DKIM/baylibre-com.20150623.gappssmtp.com (From: narmstrong@baylibre.com)
>     ---
>     Total patches: 1
>     ---
>      Link: https://lore.kernel.org/r/20210601084830.260196-1-narmstrong@baylibre.com
>      Base: not found
>            git am /tmp/20210601_narmstrong_usb_dwc3_meson_g12a_fix_usb2_phy_glue_init_when_phy0_is_disabled.mbx

This is great, thanks for changing this on the lore backend, and for all
of this work in the firstplace.

greg k-h

  reply	other threads:[~2021-06-05  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  8:48 [PATCH] usb: dwc3-meson-g12a: fix usb2 PHY glue init when phy0 is disabled Neil Armstrong
2021-06-03 18:20 ` Martin Blumenstingl
2021-06-04 10:58 ` Greg KH
2021-06-04 15:07   ` Konstantin Ryabitsev
2021-06-04 16:46     ` Konstantin Ryabitsev
2021-06-05  7:02       ` Greg KH [this message]
2021-06-07  6:46       ` Neil Armstrong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLshmr+H4mES+kZX@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).