On 2019-01-21 at 15:24:17 -0500, Michael S. Tsirkin wrote:
> On Mon, Jan 21, 2019 at 02:35:57PM +0800, Yi Zhang wrote:
> > On 2019-01-16 at 10:55:33 -0500, Michael S. Tsirkin wrote:
> > > On Wed, Jan 16, 2019 at 04:10:29PM +0800, Zhang Yi wrote:
> > > > Signed-off-by: Zhang Yi
> > > > Signed-off-b
On Mon, Jan 21, 2019 at 02:35:57PM +0800, Yi Zhang wrote:
> On 2019-01-16 at 10:55:33 -0500, Michael S. Tsirkin wrote:
> > On Wed, Jan 16, 2019 at 04:10:29PM +0800, Zhang Yi wrote:
> > > Signed-off-by: Zhang Yi
> > > Signed-off-by: Michael S. Tsirkin
> >
> > OK so if you apply this patch, do you
On 2019-01-16 at 10:55:33 -0500, Michael S. Tsirkin wrote:
> On Wed, Jan 16, 2019 at 04:10:29PM +0800, Zhang Yi wrote:
> > Signed-off-by: Zhang Yi
> > Signed-off-by: Michael S. Tsirkin
>
> OK so if you apply this patch, do you get
> any sparse warning at all?
Didn't get any sparse warning.
>
>
On Wed, Jan 16, 2019 at 04:10:29PM +0800, Zhang Yi wrote:
> Signed-off-by: Zhang Yi
> Signed-off-by: Michael S. Tsirkin
OK so if you apply this patch, do you get
any sparse warning at all?
If not how come?
And we need to ask patchew maintainers to
Overall I'd suggest that since you no longer
Signed-off-by: Zhang Yi
Signed-off-by: Michael S. Tsirkin
---
include/exec/memory.h | 12 ++--
include/qemu/osdep.h | 9 +
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 667466b..03824d9 100644
--- a/include/e
