From: Mark Rutland <mark.rutland@arm.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>, will@kernel.org
Cc: maz@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: Re: [PATCH] arm64: arch_timer: Replace HTTP links with HTTPS ones
Date: Tue, 14 Jul 2020 14:43:37 +0100 [thread overview]
Message-ID: <20200714134337.GB67386@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20200713100359.33063-1-grandmaster@al2klimov.de>
On Mon, Jul 13, 2020 at 12:03:59PM +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.
[...]
> diff --git a/arch/arm64/include/asm/arch_timer.h b/arch/arm64/include/asm/arch_timer.h
> index 9f0ec21d6327..c395b17eead4 100644
> --- a/arch/arm64/include/asm/arch_timer.h
> +++ b/arch/arm64/include/asm/arch_timer.h
> @@ -172,7 +172,7 @@ static inline void arch_timer_set_cntkctl(u32 cntkctl)
> * This insanity brought to you by speculative system register reads,
> * out-of-order memory accesses, sequence locks and Thomas Gleixner.
> *
> - * http://lists.infradead.org/pipermail/linux-arm-kernel/2019-February/631195.html
> + * https://lists.infradead.org/pipermail/linux-arm-kernel/2019-February/631195.html
This link is dead, and I'd rather replace it with a (HTTPS)
lore.kernel.org link.
IIUC that's:
https://lore.kernel.org/r/alpine.DEB.2.21.1902081950260.1662@nanos.tec.linutronix.de
... later referred to in the sub-thread:
https://lore.kernel.org/linux-arm-kernel/20190213170413.GE6346@brain-police/
Will, does that look right to you?
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-14 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 10:03 [PATCH] arm64: arch_timer: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-14 13:43 ` Mark Rutland [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=20200714134337.GB67386@C02TD0UTHF1T.local \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=grandmaster@al2klimov.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=will@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