From: "Michael Kerrisk (man-opages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 12/15] proc.5: update pointer to in-kernel MTRR documentation
Date: Mon, 11 Sep 2017 15:59:41 +0200 [thread overview]
Message-ID: <651b5000-23e8-ea77-afe3-603c8c62989d@gmail.com> (raw)
In-Reply-To: <20170911030414.GA30199-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
On 09/11/2017 05:04 AM, Eugene Syromyatnikov wrote:
> The location of the file has been changed in Linux commit
> v2.6.28-rc1~734^2^8~3.
Applied. Thanks!
Cheers,
Michael
> * man5/proc.5 (.SS Files and directories) <.TP .I /proc/mtrr>: Amend
> pointer to in-kernel MTRR documentation with the location change
> happened in Linux 2.6.28.
>
> Signed-off-by: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> man5/proc.5 | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/man5/proc.5 b/man5/proc.5
> index 9c62ee2..f469d1c 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -3319,7 +3319,11 @@ The format of this file is documented in
> .I /proc/mtrr
> Memory Type Range Registers.
> See the Linux kernel source file
> +.I Documentation/x86/mtrr.txt
> +.\" commit 7225e75144b9718cbbe1820d9c011c809d5773fd
> +(or
> .I Documentation/mtrr.txt
> +before Linux 2.6.28)
> for details.
> .TP
> .I /proc/net
>
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-09-11 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 3:04 [PATCH 12/15] proc.5: update pointer to in-kernel MTRR documentation Eugene Syromyatnikov
[not found] ` <20170911030414.GA30199-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-11 13:59 ` Michael Kerrisk (man-opages) [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=651b5000-23e8-ea77-afe3-603c8c62989d@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.