[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180102140906.GC8222@bombadil.infradead.org>
Date: Tue, 2 Jan 2018 06:09:06 -0800
From: Matthew Wilcox <willy@...radead.org>
To: Wei Wang <wei.w.wang@...el.com>
Cc: virtio-dev@...ts.oasis-open.org, linux-kernel@...r.kernel.org,
qemu-devel@...gnu.org, virtualization@...ts.linux-foundation.org,
kvm@...r.kernel.org, linux-mm@...ck.org, mst@...hat.com,
mhocko@...nel.org, akpm@...ux-foundation.org,
mawilcox@...rosoft.com, penguin-kernel@...ove.SAKURA.ne.jp
Subject: Re: [PATCH v20 3/7 RESEND] xbitmap: add more operations
On Fri, Dec 22, 2017 at 04:49:11PM +0800, Wei Wang wrote:
> Thanks for the improvement. I also found a small bug in xb_zero. With the
> following changes, it has passed the current test cases and tested with the
> virtio-balloon usage without any issue.
Thanks; I applied the change. Can you supply a test-case for testing
xb_zero please?
> > @@ -25,8 +26,11 @@ idr-test: idr-test.o $(CORE_OFILES)
> > multiorder: multiorder.o $(CORE_OFILES)
> > +xbitmap: xbitmap.o $(CORE_OFILES)
> > + $(CC) $(CFLAGS) $(LDFLAGS) $^ -o xbitmap
> > +
>
> I think the "$(CC).." line should be removed, which will fix the build error
> when adding "xbitmap" to TARGET.
Not sure what build error you're talking about, but yes that CC line
should go. Thanks, deleted.
Powered by blists - more mailing lists