From: Tony Lindgren <tony@atomide.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: khilman@kernel.org, linux@armlinux.org.uk,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for v5.9] ARM: OMAP2+: pm33xx-core: Replace HTTP links with HTTPS ones
Date: Wed, 19 Aug 2020 10:21:17 +0300 [thread overview]
Message-ID: <20200819072117.GA2994@atomide.com> (raw)
In-Reply-To: <20200719091912.57273-1-grandmaster@al2klimov.de>
* Alexander A. Klimov <grandmaster@al2klimov.de> [200719 12:27]:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
Thanks applying into omap-for-v5.10/soc.
Tony
prev parent reply other threads:[~2020-08-19 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 9:19 [PATCH for v5.9] ARM: OMAP2+: pm33xx-core: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-08-19 7:21 ` Tony Lindgren [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=20200819072117.GA2994@atomide.com \
--to=tony@atomide.com \
--cc=grandmaster@al2klimov.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).