From: Sven Roederer <devel-sven@geroedel.de>
To: linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: changes.rst: add rsync to the list of required tools
Date: Mon, 07 Dec 2020 22:38:52 +0100 [thread overview]
Message-ID: <2164238.7AY86t5Hnk@strike> (raw)
In-Reply-To: <20201002191336.7423-1-devel-sven@geroedel.de>
Am Freitag, 2. Oktober 2020, 21:13:36 CET schrieben Sie:
> Since 5.3 (59b2bd05f5f4dc) the 'make headers_install' call depends on
> rsync to deploy the files system wide.
>
> Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
> ---
> Documentation/process/changes.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/process/changes.rst
> b/Documentation/process/changes.rst index ee741763a3fc..114edabb21c8 100644
> --- a/Documentation/process/changes.rst
> +++ b/Documentation/process/changes.rst
> @@ -55,9 +55,11 @@ iptables 1.4.2 iptables -V
> openssl & libcrypto 1.0.0 openssl version
> bc 1.06.95 bc --version
> Sphinx\ [#f1]_ 1.3 sphinx-build --version
> +rsync\ [#f2]_ 3.0 rsync --version
> ====================== ===============
> ========================================
>
> .. [#f1] Sphinx is needed only to build the Kernel documentation
> +.. [#f2] rsync is needed only during final install of kernel-headers
>
> Kernel compilation
> ******************
> @@ -161,6 +163,12 @@ is not build with ``CONFIG_KALLSYMS`` and you have no
> way to rebuild and reproduce the Oops with that option, then you can still
> decode that Oops with ksymoops.
>
> +rsync
> +-----
> +
> +rsync is used to install the kernel-headers system wide with administrative
> +permissions. This was added in v5.3.
> +
> Mkinitrd
> --------
Hi, just pinging on this again. V2 of this patch was send, having the typo
fixed.
Best Sven
prev parent reply other threads:[~2020-12-07 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 21:50 [PATCH] docs: changes.rst: add rsync to the list of required tools Sven Roederer
2020-10-01 22:20 ` Matthew Wilcox
2020-10-02 19:10 ` Sven Roederer
2020-10-02 19:13 ` [PATCH v2] " Sven Roederer
2020-12-07 21:38 ` Sven Roederer [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=2164238.7AY86t5Hnk@strike \
--to=devel-sven@geroedel.de \
--cc=linux-doc@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).