From: Richard Weinberger <richard.weinberger@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Vignesh Raghavendra <vigneshr@ti.com>,
Arnd Bergmann <arnd@arndb.de>,
Richard Weinberger <richard@nod.at>,
Linus Walleij <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-mtd@lists.infradead.org,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH] mtd: Replace HTTP links with HTTPS ones
Date: Sun, 2 Aug 2020 22:18:42 +0200 [thread overview]
Message-ID: <CAFLxGvyxFjy2cSWgokb8=d_FoGCX4QVbnoLYdLqybKCypoBWLA@mail.gmail.com> (raw)
In-Reply-To: <20200721015258.GA3362089@bogus>
On Tue, Jul 21, 2020 at 3:54 AM Rob Herring <robh@kernel.org> wrote:
>
> On Mon, 13 Jul 2020 18:54:08 +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/mtd/davinci-nand.txt | 4 ++--
> > drivers/mtd/chips/Kconfig | 2 +-
> > drivers/mtd/maps/Kconfig | 2 +-
> > drivers/mtd/maps/sc520cdp.c | 2 +-
> > 4 files changed, 5 insertions(+), 5 deletions(-)
> >
>
> Acked-by: Rob Herring <robh@kernel.org>
All three mtd related patches applied to mtd/next, thanks!
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-08-02 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 16:54 [PATCH] mtd: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-21 1:52 ` Rob Herring
2020-08-02 20:18 ` Richard Weinberger [this message]
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='CAFLxGvyxFjy2cSWgokb8=d_FoGCX4QVbnoLYdLqybKCypoBWLA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grandmaster@al2klimov.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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).