linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Linux MM" <linux-mm@kvack.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Jérôme Glisse" <jglisse@redhat.com>
Subject: Re: [PATCH] mm: fix Documentation/vm/hmm.rst Sphinx warnings
Date: Tue, 21 May 2019 11:21:18 +0300	[thread overview]
Message-ID: <20190521082118.GC3589@rapoport-lnx> (raw)
In-Reply-To: <c5995359-7c82-4e47-c7be-b58a4dda0953@infradead.org>

On Mon, May 20, 2019 at 02:24:01PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
> 
> Fix Sphinx warnings in Documentation/vm/hmm.rst by using "::"
> notation and inserting a blank line.  Also add a missing ';'.
> 
> Documentation/vm/hmm.rst:292: WARNING: Unexpected indentation.
> Documentation/vm/hmm.rst:300: WARNING: Unexpected indentation.
> 
> Fixes: 023a019a9b4e ("mm/hmm: add default fault flags to avoid the need to pre-fill pfns arrays")
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jérôme Glisse <jglisse@redhat.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>

Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>

> ---
>  Documentation/vm/hmm.rst |    8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> --- lnx-52-rc1.orig/Documentation/vm/hmm.rst
> +++ lnx-52-rc1/Documentation/vm/hmm.rst
> @@ -288,15 +288,17 @@ For instance if the device flags for dev
>      WRITE (1 << 62)
> 
>  Now let say that device driver wants to fault with at least read a range then
> -it does set:
> -    range->default_flags = (1 << 63)
> +it does set::
> +
> +    range->default_flags = (1 << 63);
>      range->pfn_flags_mask = 0;
> 
>  and calls hmm_range_fault() as described above. This will fill fault all page
>  in the range with at least read permission.
> 
>  Now let say driver wants to do the same except for one page in the range for
> -which its want to have write. Now driver set:
> +which its want to have write. Now driver set::
> +
>      range->default_flags = (1 << 63);
>      range->pfn_flags_mask = (1 << 62);
>      range->pfns[index_of_write] = (1 << 62);
> 
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2019-05-21  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 21:24 Randy Dunlap
2019-05-21  8:21 ` Mike Rapoport [this message]
2019-05-21 16:35   ` Jerome Glisse

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=20190521082118.GC3589@rapoport-lnx \
    --to=rppt@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=jglisse@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.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