From: Jens Axboe <axboe@kernel.dk>
To: Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org
Cc: Joe Perches <joe@perches.com>, Justin Sanders <justin@coraid.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] block: Replace lkml.org links with lore
Date: Wed, 10 Feb 2021 20:07:43 -0700 [thread overview]
Message-ID: <8cdd00cd-c17f-fe69-fa07-b144a64c55e5@kernel.dk> (raw)
In-Reply-To: <20210210235159.3190756-1-keescook@chromium.org>
On 2/10/21 4:51 PM, Kees Cook wrote:
> As started by commit 05a5f51ca566 ("Documentation: Replace lkml.org
> links with lore"), replace lkml.org links with lore to better use a
> single source that's more likely to stay available long-term.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2021-02-11 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 23:51 [PATCH] block: Replace lkml.org links with lore Kees Cook
2021-02-11 3:07 ` Jens Axboe [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=8cdd00cd-c17f-fe69-fa07-b144a64c55e5@kernel.dk \
--to=axboe@kernel.dk \
--cc=joe@perches.com \
--cc=justin@coraid.com \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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).