From: Alex Williamson <alex.williamson@redhat.com>
To: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Eric Auger <eric.auger@linaro.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] vfio: fix wrong initialize vfio_group_list
Date: Sun, 25 Jan 2015 21:39:20 -0500 (EST) [thread overview]
Message-ID: <2091737990.255560.1422239960803.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <54C5A408.5000001@cn.fujitsu.com>
----- Original Message -----
>
> On 01/26/2015 10:06 AM, Alex Williamson wrote:
> >
> > ----- Original Message -----
> >> CC: qemu-trivial@nongnu.org
> >>
> >> On 01/22/2015 04:14 PM, Eric Auger wrote:
> >>> Hi Chen,
> >>>
> >>> thanks for correcting this mistake I introduced when moving code from
> >>> pci to common.
> >> so, can you check in this patch?
> > I've got it queued up and while it's clearly an error, I don't see that the
> > fix actually changes the resulting code, the parameter is ignored in the
> > macro. Am I missing something? If that's the case, I'll include it in my
> > next pull request, but I don't see any pressing reason to rush that
> > request. Thanks,
> Yes, this patch can not affect the result of the code execution for
> now, but I think it is also a typo mistake, if the macro
> QLIST_HEAD_INITIALIZER
> will be changed and using the parameter in the future, this error will
> be difficultly found. I think the earlier found the earlier fixed.
Yes, it's obviously an error and I'll get it in before QEMU 2.3, likely within the next week or so. Thanks,
Alex
> >>> On 01/22/2015 04:50 AM, Chen Fan wrote:
> >>>> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> >>>> ---
> >>>> hw/vfio/common.c | 2 +-
> >>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> >>>> index cf483ff..e71385e 100644
> >>>> --- a/hw/vfio/common.c
> >>>> +++ b/hw/vfio/common.c
> >>>> @@ -32,7 +32,7 @@
> >>>> #include "trace.h"
> >>>>
> >>>> struct vfio_group_head vfio_group_list =
> >>>> - QLIST_HEAD_INITIALIZER(vfio_address_spaces);
> >>>> + QLIST_HEAD_INITIALIZER(vfio_group_list);
> >>>> struct vfio_as_head vfio_address_spaces =
> >>>> QLIST_HEAD_INITIALIZER(vfio_address_spaces);
> >>>>
> >>>>
> >>
> > .
> >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Eric Auger <eric.auger@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] vfio: fix wrong initialize vfio_group_list
Date: Sun, 25 Jan 2015 21:39:20 -0500 (EST) [thread overview]
Message-ID: <2091737990.255560.1422239960803.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <54C5A408.5000001@cn.fujitsu.com>
----- Original Message -----
>
> On 01/26/2015 10:06 AM, Alex Williamson wrote:
> >
> > ----- Original Message -----
> >> CC: qemu-trivial@nongnu.org
> >>
> >> On 01/22/2015 04:14 PM, Eric Auger wrote:
> >>> Hi Chen,
> >>>
> >>> thanks for correcting this mistake I introduced when moving code from
> >>> pci to common.
> >> so, can you check in this patch?
> > I've got it queued up and while it's clearly an error, I don't see that the
> > fix actually changes the resulting code, the parameter is ignored in the
> > macro. Am I missing something? If that's the case, I'll include it in my
> > next pull request, but I don't see any pressing reason to rush that
> > request. Thanks,
> Yes, this patch can not affect the result of the code execution for
> now, but I think it is also a typo mistake, if the macro
> QLIST_HEAD_INITIALIZER
> will be changed and using the parameter in the future, this error will
> be difficultly found. I think the earlier found the earlier fixed.
Yes, it's obviously an error and I'll get it in before QEMU 2.3, likely within the next week or so. Thanks,
Alex
> >>> On 01/22/2015 04:50 AM, Chen Fan wrote:
> >>>> Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
> >>>> ---
> >>>> hw/vfio/common.c | 2 +-
> >>>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> >>>> index cf483ff..e71385e 100644
> >>>> --- a/hw/vfio/common.c
> >>>> +++ b/hw/vfio/common.c
> >>>> @@ -32,7 +32,7 @@
> >>>> #include "trace.h"
> >>>>
> >>>> struct vfio_group_head vfio_group_list =
> >>>> - QLIST_HEAD_INITIALIZER(vfio_address_spaces);
> >>>> + QLIST_HEAD_INITIALIZER(vfio_group_list);
> >>>> struct vfio_as_head vfio_address_spaces =
> >>>> QLIST_HEAD_INITIALIZER(vfio_address_spaces);
> >>>>
> >>>>
> >>
> > .
> >
>
>
next prev parent reply other threads:[~2015-01-26 2:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 3:50 [Qemu-devel] [PATCH] vfio: fix wrong initialize vfio_group_list Chen Fan
2015-01-22 8:14 ` Eric Auger
2015-01-26 1:06 ` [Qemu-trivial] " Chen Fan
2015-01-26 1:06 ` Chen Fan
2015-01-26 2:06 ` [Qemu-trivial] " Alex Williamson
2015-01-26 2:06 ` Alex Williamson
2015-01-26 2:18 ` [Qemu-trivial] " Chen Fan
2015-01-26 2:18 ` Chen Fan
2015-01-26 2:39 ` Alex Williamson [this message]
2015-01-26 2:39 ` Alex Williamson
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=2091737990.255560.1422239960803.JavaMail.zimbra@redhat.com \
--to=alex.williamson@redhat.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=eric.auger@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.