From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] doc/memory.txt: fix typo
Date: Thu, 25 Feb 2016 18:05:43 +0800 [thread overview]
Message-ID: <56CED1F7.8070305@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA944NgbOvv3mYH2xvEup2V-UevPXPfew=Y2N7sYkvvxpQ@mail.gmail.com>
On 02/25/2016 06:00 PM, Peter Maydell wrote:
> On 25 February 2016 at 09:32, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>> to match structure MemoryRegionOps definition
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>> ---
>> And there seems are some out of date content in this file, like
>> "cpu_register_io_memory()" mentioned in the last line, which is removed several
>> years ago in commit 97161e177. I am sure how to modify it, So I take the
>> liberty to CC the guys in the cc-list(get list from get_maintainer.pl).k
>
Hi peter,
Thanks for your quick response.
Can`t believe I miss a "not" in my word..."I am not sure how to modify
it" so I CC you guys:)
--
Yours Sincerely,
Cao jin
WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] doc/memory.txt: fix typo
Date: Thu, 25 Feb 2016 18:05:43 +0800 [thread overview]
Message-ID: <56CED1F7.8070305@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA944NgbOvv3mYH2xvEup2V-UevPXPfew=Y2N7sYkvvxpQ@mail.gmail.com>
On 02/25/2016 06:00 PM, Peter Maydell wrote:
> On 25 February 2016 at 09:32, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>> to match structure MemoryRegionOps definition
>>
>> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
>> ---
>> And there seems are some out of date content in this file, like
>> "cpu_register_io_memory()" mentioned in the last line, which is removed several
>> years ago in commit 97161e177. I am sure how to modify it, So I take the
>> liberty to CC the guys in the cc-list(get list from get_maintainer.pl).k
>
Hi peter,
Thanks for your quick response.
Can`t believe I miss a "not" in my word..."I am not sure how to modify
it" so I CC you guys:)
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-02-25 10:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 9:32 [Qemu-trivial] [PATCH] doc/memory.txt: fix typo Cao jin
2016-02-25 9:32 ` [Qemu-devel] " Cao jin
2016-02-25 10:00 ` [Qemu-trivial] " Peter Maydell
2016-02-25 10:00 ` Peter Maydell
2016-02-25 10:05 ` Cao jin [this message]
2016-02-25 10:05 ` Cao jin
2016-02-25 13:30 ` [Qemu-trivial] " Cao jin
2016-02-25 13:30 ` Cao jin
2016-02-25 14:24 ` [Qemu-trivial] " Peter Maydell
2016-02-25 14:24 ` Peter Maydell
2016-02-26 2:36 ` [Qemu-trivial] " Cao jin
2016-02-26 2:36 ` Cao jin
2016-03-03 14:45 ` [Qemu-trivial] " Paolo Bonzini
2016-03-03 14:45 ` Paolo Bonzini
2016-03-03 14:54 ` [Qemu-trivial] " Peter Maydell
2016-03-03 14:54 ` Peter Maydell
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=56CED1F7.8070305@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.