linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH V2] docs/mm: concepts.rst: remove unnecessary word
Date: Tue, 21 Jul 2020 14:37:31 +0300	[thread overview]
Message-ID: <20200721113731.GH802087@linux.ibm.com> (raw)
In-Reply-To: <20200721112251.6100-1-unixbhaskar@gmail.com>

On Tue, Jul 21, 2020 at 04:52:51PM +0530, Bhaskar Chowdhury wrote:
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

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

> ---
> Mike,
>  I have made the change to the subject line as you mentioned in previous
>  mail.
> 
>  Documentation/admin-guide/mm/concepts.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/mm/concepts.rst b/Documentation/admin-guide/mm/concepts.rst
> index c2531b14bf46..fa0974fbeae7 100644
> --- a/Documentation/admin-guide/mm/concepts.rst
> +++ b/Documentation/admin-guide/mm/concepts.rst
> @@ -35,7 +35,7 @@ physical memory (demand paging) and provides a mechanism for the
>  protection and controlled sharing of data between processes.
>  
>  With virtual memory, each and every memory access uses a virtual
> -address. When the CPU decodes the an instruction that reads (or
> +address. When the CPU decodes an instruction that reads (or
>  writes) from (or to) the system memory, it translates the `virtual`
>  address encoded in that instruction to a `physical` address that the
>  memory controller can understand.
> -- 
> 2.26.2
> 

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2020-07-21 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 11:22 [PATCH V2] docs/mm: concepts.rst: remove unnecessary word Bhaskar Chowdhury
2020-07-21 11:37 ` Mike Rapoport [this message]
2020-07-23 20:03 ` Jonathan Corbet

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=20200721113731.GH802087@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=unixbhaskar@gmail.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;
as well as URLs for NNTP newsgroup(s).