public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Richard Guy Briggs <rgb@redhat.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: corrected sub-chapter number
Date: Tue, 17 Jun 2014 10:27:35 -0700	[thread overview]
Message-ID: <53A07A87.3010908@infradead.org> (raw)
In-Reply-To: <1537cb738c6d4998106c5b91626b69f742d2b47d.1402946960.git.rgb@redhat.com>

On 06/16/14 12:48, Richard Guy Briggs wrote:
> The index is correct, but there are two sections tagged 3.7.  Fix.
> 
> Signed-off-by: Richard Guy Briggs <rgb@redhat.com>

This seems to already be fixed by commit 49d063cb353265c3af701bab215ac438ca7df36d
on April 7, 2014.

> ---
>  Documentation/filesystems/proc.txt |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
> index f00bee1..68e3a76 100644
> --- a/Documentation/filesystems/proc.txt
> +++ b/Documentation/filesystems/proc.txt
> @@ -1648,7 +1648,7 @@ pids, so one need to either stop or freeze processes being inspected
>  if precise results are needed.
>  
>  
> -3.7	/proc/<pid>/fdinfo/<fd> - Information about opened file
> +3.8	/proc/<pid>/fdinfo/<fd> - Information about opened file
>  ---------------------------------------------------------------
>  This file provides information associated with an opened file. The regular
>  files have at least two fields -- 'pos' and 'flags'. The 'pos' represents
> 


-- 
~Randy

  reply	other threads:[~2014-06-17 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 19:48 [PATCH] Documentation: corrected sub-chapter number Richard Guy Briggs
2014-06-17 17:27 ` Randy Dunlap [this message]
2014-06-17 20:51   ` Richard Guy Briggs

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=53A07A87.3010908@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgb@redhat.com \
    /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