All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: rppt@linux.vnet.ibm.com, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Made single word change in fourth paragraph for right sentence construction
Date: Tue, 21 Jul 2020 13:47:54 +0300	[thread overview]
Message-ID: <20200721104754.GG802087@linux.ibm.com> (raw)
In-Reply-To: <20200721101933.32500-1-unixbhaskar@gmail.com>

Hi,

On Tue, Jul 21, 2020 at 03:49:34PM +0530, Bhaskar Chowdhury wrote:
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Mike/Jon,
>  it is nit ...but catch my eyes while reading...so the patch.

That's the right approach! :)

It would be great if you could update the patch subject to better
describe the context and the actual change, e.g:

docs/mm: concepts.rst: remove unnecessary article
 
>  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 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 10:19 [PATCH] Made single word change in fourth paragraph for right sentence construction Bhaskar Chowdhury
2020-07-21 10:47 ` Mike Rapoport [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=20200721104754.GG802087@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --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 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.