All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: zhaolichang <zhaolichang@huawei.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH RFC 03/10] docs/: fix some comment spelling errors
Date: Mon, 24 Aug 2020 13:35:25 +0100	[thread overview]
Message-ID: <CAFEAcA8yMc+R+v_jhWeKPKWmjhR0VpfphLeK9PS0E+YtMDh-yQ@mail.gmail.com> (raw)
In-Reply-To: <20200812101500.2066-4-zhaolichang@huawei.com>

On Wed, 12 Aug 2020 at 14:43, zhaolichang <zhaolichang@huawei.com> wrote:
>
> I found that there are many spelling errors in the comments of qemu,
> so I used the spellcheck tool to check the spelling errors
> and finally found some spelling errors in the docs folder.
>
> Signed-off-by: zhaolichang <zhaolichang@huawei.com>

> --- a/docs/devel/tracing.txt
> +++ b/docs/devel/tracing.txt
> @@ -55,7 +55,7 @@ without any sub-directory path prefix. eg io/channel-buffer.c would do
>    #include "trace.h"
>
>  To access the 'io/trace.h' file. While it is possible to include a trace.h
> -file from outside a source files' own sub-directory, this is discouraged in
> +file from outside a source files own sub-directory, this is discouraged in

should be "file's".

>  general. It is strongly preferred that all events be declared directly in
>  the sub-directory that uses them. The only exception is where there are some
>  shared trace events defined in the top level directory trace-events file.

Otherwise
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>

thanks
-- PMM


  parent reply	other threads:[~2020-08-24 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 10:14 [PATCH RFC 00/10] fix some comment spelling errors zhaolichang
2020-08-12 10:14 ` [PATCH RFC 01/10] qemu/: " zhaolichang
2020-08-12 14:12   ` Alex Bennée
2020-08-24 14:33     ` Eric Blake
2020-08-12 10:14 ` [PATCH RFC 02/10] migration/: " zhaolichang
2020-08-24 12:32   ` Peter Maydell
2020-08-12 10:14 ` [PATCH RFC 03/10] docs/: " zhaolichang
2020-08-12 14:13   ` Alex Bennée
2020-08-24 12:35   ` Peter Maydell [this message]
2020-08-12 10:14 ` [PATCH RFC 04/10] scripts/: " zhaolichang
2020-08-24 12:30   ` Peter Maydell
2020-08-12 10:14 ` [PATCH RFC 05/10] util/: " zhaolichang
2020-08-12 14:14   ` Alex Bennée
2020-08-12 10:14 ` [PATCH RFC 06/10] linux-user/: " zhaolichang
2020-08-12 14:15   ` Alex Bennée
2020-08-12 10:14 ` [PATCH RFC 07/10] block/: " zhaolichang
2020-08-24 12:28   ` Peter Maydell
2020-08-12 10:14 ` [PATCH RFC 08/10] disas/: " zhaolichang
2020-08-24 12:29   ` Peter Maydell
2020-08-12 10:14 ` [PATCH RFC 09/10] qapi/: " zhaolichang
2020-08-24 12:25   ` Markus Armbruster
2020-08-12 10:15 ` [PATCH RFC 10/10] contrib/: " zhaolichang
2020-08-12 14:16   ` Alex Bennée
2020-08-24 12:22 ` [PATCH RFC 00/10] " Markus Armbruster

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=CAFEAcA8yMc+R+v_jhWeKPKWmjhR0VpfphLeK9PS0E+YtMDh-yQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhaolichang@huawei.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.