From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <qemu-devel@nongnu.org>, <qemu-trivial@nongnu.org>
Cc: <alex.williamson@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH 1/2] vfio: remove a duplicated word in comments
Date: Wed, 21 Dec 2016 14:29:16 +0800 [thread overview]
Message-ID: <585A213C.4090706@cn.fujitsu.com> (raw)
In-Reply-To: <1478833296-25853-1-git-send-email-caoj.fnst@cn.fujitsu.com>
ping
On 11/11/2016 11:01 AM, Cao jin wrote:
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> hw/vfio/pci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 31aaecb..c94987c 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -1881,8 +1881,8 @@ static void vfio_add_ext_cap(VFIOPCIDevice *vdev)
> * 0 is reserved for this since absence of capabilities is indicated by
> * 0 for the ID, version, AND next pointer. However, pcie_add_capability()
> * uses ID 0 as reserved for list management and will incorrectly match and
> - * assert if we attempt to pre-load the head of the chain with with this
> - * ID. Use ID 0xFFFF temporarily since it is also seems to be reserved in
> + * assert if we attempt to pre-load the head of the chain with this ID.
> + * Use ID 0xFFFF temporarily since it is also seems to be reserved in
> * part for identifying absence of capabilities in a root complex register
> * block. If the ID still exists after adding capabilities, switch back to
> * zero. We'll mark this entire first dword as emulated for this purpose.
>
--
Sincerely,
Cao jin
WARNING: multiple messages have this Message-ID (diff)
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: alex.williamson@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] vfio: remove a duplicated word in comments
Date: Wed, 21 Dec 2016 14:29:16 +0800 [thread overview]
Message-ID: <585A213C.4090706@cn.fujitsu.com> (raw)
In-Reply-To: <1478833296-25853-1-git-send-email-caoj.fnst@cn.fujitsu.com>
ping
On 11/11/2016 11:01 AM, Cao jin wrote:
> Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com>
> ---
> hw/vfio/pci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
> index 31aaecb..c94987c 100644
> --- a/hw/vfio/pci.c
> +++ b/hw/vfio/pci.c
> @@ -1881,8 +1881,8 @@ static void vfio_add_ext_cap(VFIOPCIDevice *vdev)
> * 0 is reserved for this since absence of capabilities is indicated by
> * 0 for the ID, version, AND next pointer. However, pcie_add_capability()
> * uses ID 0 as reserved for list management and will incorrectly match and
> - * assert if we attempt to pre-load the head of the chain with with this
> - * ID. Use ID 0xFFFF temporarily since it is also seems to be reserved in
> + * assert if we attempt to pre-load the head of the chain with this ID.
> + * Use ID 0xFFFF temporarily since it is also seems to be reserved in
> * part for identifying absence of capabilities in a root complex register
> * block. If the ID still exists after adding capabilities, switch back to
> * zero. We'll mark this entire first dword as emulated for this purpose.
>
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2016-12-21 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 3:01 [Qemu-trivial] [PATCH 1/2] vfio: remove a duplicated word in comments Cao jin
2016-11-11 3:01 ` [Qemu-devel] " Cao jin
2016-12-21 6:29 ` Cao jin [this message]
2016-12-21 6:29 ` Cao jin
2017-01-12 11:08 ` [Qemu-trivial] " Michael Tokarev
2017-01-12 11:08 ` [Qemu-devel] " Michael Tokarev
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=585A213C.4090706@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=alex.williamson@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 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.