qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Mao Zhongyi <maozhongyi@cmss.chinamobile.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com,
	"qemu-trivial@nongnu.org >> QEMU Trivial"
	<qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] pci_bridge: fix a typo in comment
Date: Thu, 8 Nov 2018 14:12:33 +0100	[thread overview]
Message-ID: <1898dc23-c512-88bd-cb73-5a2cffccd176@redhat.com> (raw)
In-Reply-To: <20181108122102.9915-1-maozhongyi@cmss.chinamobile.com>

Cc'ing qemu-trivial@

On 8/11/18 13:21, Mao Zhongyi wrote:
> Signed-off-by: Mao Zhongyi <maozhongyi@cmss.chinamobile.com>

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

> ---
>   hw/pci/pci_bridge.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/hw/pci/pci_bridge.c b/hw/pci/pci_bridge.c
> index ee9dff2d3a..da8daa3ff2 100644
> --- a/hw/pci/pci_bridge.c
> +++ b/hw/pci/pci_bridge.c
> @@ -310,7 +310,7 @@ void pci_bridge_reset(DeviceState *qdev)
>   
>       /*
>        * the default values for base/limit registers aren't specified
> -     * in the PCI-to-PCI-bridge spec. So we don't thouch them here.
> +     * in the PCI-to-PCI-bridge spec. So we don't touch them here.
>        * Each implementation can override it.
>        * typical implementation does
>        * zero base/limit registers or
> 

  reply	other threads:[~2018-11-08 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 12:21 [Qemu-devel] [PATCH] pci_bridge: fix a typo in comment Mao Zhongyi
2018-11-08 13:12 ` Philippe Mathieu-Daudé [this message]
2019-10-23  3:32   ` maozy
2019-10-23 10:47     ` Philippe Mathieu-Daudé
2019-10-24 17:25       ` Laurent Vivier
  -- strict thread matches above, loose matches on Subject: below --
2019-09-09  3:14 Mao Zhongyi
2019-09-09  9:28 ` Philippe Mathieu-Daudé

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=1898dc23-c512-88bd-cb73-5a2cffccd176@redhat.com \
    --to=philmd@redhat.com \
    --cc=maozhongyi@cmss.chinamobile.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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;
as well as URLs for NNTP newsgroup(s).