From: Kees Cook <keescook@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Bjorn Helgaas <helgaas@kernel.org>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
bhelgaas@google.com, robh+dt@kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
kishon@ti.com, lorenzo.pieralisi@arm.com, hongxing.zhu@nxp.com,
l.stach@pengutronix.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com, m-karicheri2@ti.com,
songxiaowei@hisilicon.com, wangbinghui@hisilicon.com,
amurray@thegoodpenguin.co.uk,
sathyanarayanan.kuppuswamy@linux.intel.com, hkallweit1@gmail.com,
rafael.j.wysocki@intel.com, rdunlap@infradead.org,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Documentation: Replace lkml.org links with lore
Date: Tue, 9 Feb 2021 23:28:43 -0800 [thread overview]
Message-ID: <202102092327.F6D8335A7@keescook> (raw)
In-Reply-To: <77cdb7f32cfb087955bfc3600b86c40bed5d4104.camel@perches.com>
On Sun, Jan 10, 2021 at 12:41:44PM -0800, Joe Perches wrote:
> Replace the lkml.org links with lore to better use a single source
> that's more likely to stay available long-term.
What's the best way to teach checkpatch about this? I couldn't find the
right place to do it. (And more generally, can it also suggest https
over http?)
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Joe Perches <joe@perches.com>
Cc: sathyanarayanan.kuppuswamy@linux.intel.com,
rafael.j.wysocki@intel.com, linux-doc@vger.kernel.org,
linux-pci@vger.kernel.org, wangbinghui@hisilicon.com,
hpa@zytor.com, festevam@gmail.com, lorenzo.pieralisi@arm.com,
Jonathan Corbet <corbet@lwn.net>,
x86@kernel.org, kishon@ti.com, hkallweit1@gmail.com,
m-karicheri2@ti.com, Bjorn Helgaas <helgaas@kernel.org>,
linux-imx@nxp.com, songxiaowei@hisilicon.com,
devicetree@vger.kernel.org, hongxing.zhu@nxp.com,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
s.hauer@pengutronix.de, robh+dt@kernel.org, bp@alien8.de,
bhelgaas@google.com, tglx@linutronix.de,
linux-omap@vger.kernel.org, mingo@redhat.com,
linux-arm-kernel@lists.infradead.org, rdunlap@infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
amurray@thegoodpenguin.co.uk, shawnguo@kernel.org,
l.stach@pengutronix.de
Subject: Re: [PATCH] Documentation: Replace lkml.org links with lore
Date: Tue, 9 Feb 2021 23:28:43 -0800 [thread overview]
Message-ID: <202102092327.F6D8335A7@keescook> (raw)
In-Reply-To: <77cdb7f32cfb087955bfc3600b86c40bed5d4104.camel@perches.com>
On Sun, Jan 10, 2021 at 12:41:44PM -0800, Joe Perches wrote:
> Replace the lkml.org links with lore to better use a single source
> that's more likely to stay available long-term.
What's the best way to teach checkpatch about this? I couldn't find the
right place to do it. (And more generally, can it also suggest https
over http?)
--
Kees Cook
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-02-10 7:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 10:30 [PATCH] Replace HTTP links with HTTPS ones: PCI Alexander A. Klimov
2020-06-27 10:30 ` Alexander A. Klimov
2020-06-30 18:07 ` Bjorn Helgaas
2020-06-30 18:07 ` Bjorn Helgaas
2020-06-30 18:09 ` PCI: Replace lkml.org, spinics, gmane with lore.kernel.org Bjorn Helgaas
2020-06-30 18:09 ` Bjorn Helgaas
2020-06-30 20:01 ` Bjorn Helgaas
2020-06-30 20:01 ` Bjorn Helgaas
2020-06-30 20:04 ` Jonathan Corbet
2020-06-30 20:04 ` Jonathan Corbet
2020-07-01 5:35 ` Joe Perches
2020-07-01 5:35 ` Joe Perches
2020-07-02 20:19 ` Joe Perches
2020-07-02 20:19 ` Joe Perches
2021-01-10 20:41 ` [PATCH] Documentation: Replace lkml.org links with lore Joe Perches
2021-01-10 20:41 ` Joe Perches
2021-01-11 19:48 ` Jonathan Corbet
2021-01-11 19:48 ` Jonathan Corbet
2021-02-10 7:28 ` Kees Cook [this message]
2021-02-10 7:28 ` Kees Cook
2021-02-10 7:41 ` Joe Perches
2021-02-10 7:41 ` Joe Perches
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=202102092327.F6D8335A7@keescook \
--to=keescook@chromium.org \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=grandmaster@al2klimov.de \
--cc=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m-karicheri2@ti.com \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=shawnguo@kernel.org \
--cc=songxiaowei@hisilicon.com \
--cc=tglx@linutronix.de \
--cc=wangbinghui@hisilicon.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.