devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, pavel@ucw.cz, dmurphy@ti.com
Subject: Re: [PATCH] leds: Replace HTTP links with HTTPS ones
Date: Mon, 20 Jul 2020 19:52:32 -0600	[thread overview]
Message-ID: <20200721015232.GA3361404@bogus> (raw)
In-Reply-To: <20200713145115.35121-1-grandmaster@al2klimov.de>

On Mon, 13 Jul 2020 16:51:15 +0200, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
> 
> Deterministic algorithm:
> For each file:
>   If not .svg:
>     For each line:
>       If doesn't contain `\bxmlns\b`:
>         For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
> 	  If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
>             If both the HTTP and HTTPS versions
>             return 200 OK and serve the same content:
>               Replace HTTP with HTTPS.
> 
> Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
> ---
>  Continuing my work started at 93431e0607e5.
>  See also: git log --oneline '--author=Alexander A. Klimov <grandmaster@al2klimov.de>' v5.7..master
>  (Actually letting a shell for loop submit all this stuff for me.)
> 
>  If there are any URLs to be removed completely or at least not just HTTPSified:
>  Just clearly say so and I'll *undo my change*.
>  See also: https://lkml.org/lkml/2020/6/27/64
> 
>  If there are any valid, but yet not changed URLs:
>  See: https://lkml.org/lkml/2020/6/26/837
> 
>  If you apply the patch, please let me know.
> 
>  Sorry again to all maintainers who complained about subject lines.
>  Now I realized that you want an actually perfect prefixes,
>  not just subsystem ones.
>  I tried my best...
>  And yes, *I could* (at least half-)automate it.
>  Impossible is nothing! :)
> 
> 
>  Documentation/devicetree/bindings/leds/leds-lm3532.txt  | 2 +-
>  Documentation/devicetree/bindings/leds/leds-lm3601x.txt | 4 ++--
>  Documentation/devicetree/bindings/leds/leds-lm36274.txt | 2 +-
>  Documentation/devicetree/bindings/leds/leds-lm3692x.txt | 2 +-
>  Documentation/devicetree/bindings/leds/leds-lm3697.txt  | 2 +-
>  Documentation/devicetree/bindings/leds/leds-lp8860.txt  | 2 +-
>  drivers/leds/leds-lm3532.c                              | 4 ++--
>  drivers/leds/leds-lm3601x.c                             | 2 +-
>  drivers/leds/leds-lm36274.c                             | 2 +-
>  drivers/leds/leds-lm3692x.c                             | 2 +-
>  drivers/leds/leds-lm3697.c                              | 2 +-
>  11 files changed, 13 insertions(+), 13 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-07-21  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 14:51 [PATCH] leds: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-21  1:52 ` Rob Herring [this message]
2020-07-21 12:21 ` Dan Murphy
2020-07-22 12:49 ` Pavel Machek

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=20200721015232.GA3361404@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=grandmaster@al2klimov.de \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    /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).