All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Lichang Zhao <zhaolichang@huawei.com>,
	 "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH V2 00/14] fix some comment spelling errors
Date: Tue, 20 Oct 2020 08:42:24 +0200	[thread overview]
Message-ID: <CAAdtpL5HZzb+_gAyNGQfM1N7vBxmLck2TXiGohv9D9dgO16cRw@mail.gmail.com> (raw)
In-Reply-To: <a5a68476-0ed8-08f9-f993-464317d798bf@huawei.com>

You forgot to Cc qemu-devel@.

(See https://wiki.qemu.org/Contribute/SubmitAPatch#CC_the_relevant_maintainer)

On Tue, Oct 20, 2020 at 4:46 AM Lichang Zhao <zhaolichang@huawei.com> wrote:

Now your name is properly displayed, so I assume you finally ran:

$ git config user.name "Lichang Zhao".

To fix how your name is displayed in your previous contributions,
consider sending this patch:

-- >8 --
diff --git a/.mailmap b/.mailmap
index 663819fb017..a56c5ba5ee1 100644
--- a/.mailmap
+++ b/.mailmap
@@ -113,6 +113,7 @@ Liu Yu <yu.liu@freescale.com>
Liu Yu <Yu.Liu@freescale.com>
Li Zhang <zhlcindy@gmail.com>
Li Zhang <zhlcindy@linux.vnet.ibm.com>
+Lichang Zhao <zhaolichang@huawei.com>
Lluís Vilanova <vilanova@ac.upc.edu>
Lluís Vilanova <xscript@gmx.net>
Longpeng (Mike) <longpeng2@huawei.com>

---

(or Ack-by it here and I'll send it).

>
> On 2020/10/9 14:44, zhaolichang wrote:
> > I found that there are many spelling errors in the comments of qemu/target/.
> >
> > I used spellcheck to check the spelling errors and found some errors in the folder.
> >
> >
> >
> > The checkpatch.pl file in the Linux kernel can check spelling errors in patches.
> >
> > I'm trying to add this function to the checkpatch.pl in qemu,
> >
> > so that no similar spelling errors will occur in the feture.
> >
> > It's not done yet and I will commit the patch when it's done.
> >
> >
> >
> > v1 -> v2:
> >
> >   add reviewed-by for patch
> >
> >
> >
> > Signed-off-by: zhaolichang <zhaolichang@huawei.com>
> >
>
> ping
> This series of patches have been reviewed. Can you help me to pull them?
>


  parent reply	other threads:[~2020-10-20  6:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  6:44 [PATCH V2 00/14] fix some comment spelling errors zhaolichang
2020-10-09  6:44 ` [PATCH V2 01/14] cris/: " zhaolichang
2020-10-09 13:14   ` Eric Blake
2020-10-09  6:44 ` [PATCH V2 02/14] ppc/: " zhaolichang
2020-10-26  9:14   ` Thomas Huth
2020-10-26 10:04     ` Greg Kurz
2020-10-27  2:05     ` David Gibson
2020-10-27  2:07   ` David Gibson
2020-10-09  6:44 ` [PATCH V2 03/14] riscv/: " zhaolichang
2020-10-09  7:15   ` Bin Meng
2020-10-09  6:44 ` [PATCH V2 04/14] rx/: " zhaolichang
2020-10-26 22:14   ` Philippe Mathieu-Daudé
2020-10-09  6:44 ` [PATCH V2 05/14] tricore/: " zhaolichang
2020-10-09  6:44 ` [PATCH V2 06/14] mips/: " zhaolichang
2020-10-09 14:36   ` Philippe Mathieu-Daudé
2020-10-09 15:15     ` Philippe Mathieu-Daudé
2020-10-09  6:44 ` [PATCH V2 07/14] s390x/: " zhaolichang
2020-10-09  7:31   ` Thomas Huth
2020-10-09  6:44 ` [PATCH V2 08/14] m68k/: " zhaolichang
2020-12-12 17:10   ` Laurent Vivier
2020-12-12 17:56     ` Philippe Mathieu-Daudé
2020-12-12 19:58       ` Laurent Vivier
2020-12-12 20:04         ` Philippe Mathieu-Daudé
2020-10-09  6:44 ` [PATCH V2 09/14] sh4/: " zhaolichang
2020-10-25  0:37   ` Philippe Mathieu-Daudé
2020-10-09  6:44 ` [PATCH V2 10/14] i386/: " zhaolichang
2020-10-09  6:44 ` [PATCH V2 11/14] avr/: " zhaolichang
2020-10-09  6:44 ` [PATCH V2 12/14] arm/: " zhaolichang
2020-10-09  6:44 ` [PATCH V2 13/14] alpha/: " zhaolichang
2020-10-09  6:44 ` [PATCH V2 14/14] target/: " zhaolichang
2020-10-09  7:12 ` [PATCH V2 00/14] " no-reply
     [not found] ` <a5a68476-0ed8-08f9-f993-464317d798bf@huawei.com>
2020-10-20  6:42   ` Philippe Mathieu-Daudé [this message]
2020-10-29  2:22     ` Lichang Zhao

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=CAAdtpL5HZzb+_gAyNGQfM1N7vBxmLck2TXiGohv9D9dgO16cRw@mail.gmail.com \
    --to=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --cc=mjt@tls.msk.ru \
    --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.