> -----Original Message-----
> From: David Marchand <david.march...@redhat.com>
> Sent: Tuesday, October 19, 2021 11:21 PM
> To: Peng, ZhihongX <zhihongx.p...@intel.com>
> Cc: Burakov, Anatoly <anatoly.bura...@intel.com>; Ananyev, Konstantin
> <konstantin.anan...@intel.com>; step...@networkplumber.org;
> Dumitrescu, Cristian <cristian.dumitre...@intel.com>; Mcnamara, John
> <john.mcnam...@intel.com>; Richardson, Bruce
> <bruce.richard...@intel.com>; dev@dpdk.org; Lin, Xueqin
> <xueqin....@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v12 1/4] Enable ASan Address Sanitization
> 
> On Tue, Oct 19, 2021 at 4:50 PM Peng, ZhihongX <zhihongx.p...@intel.com>
> wrote:
> > The v12 version has been submitted, and patch 3 and 4 has been acked.
> >
> > V10 information:
> >
> > I have compiled passed on the x86/arm/ppc platforms, directory targets  as
> below :
> > build-arm64-bluefield  build-arm64-host-clang  build-clang-shared  build-
> gcc-shared  build-ppc64le-power8
> > build-arm64-dpaa build-arm64-octeontx2   build-clang-static  build-gcc-
> static  build-x86-generic
> >
> > We do not support the windows platform due to standard google
> > document(https://github.com/google/sanitizers/wiki/AddressSanitizer)
> > also not support this.
> > We also sent our cross-compilation log to you in an other email. Passed to
> run unit test  for dpdk-testpmd simple on x86 platform.
> > What else is blocking the process ?
> > What's any action we should do for the code merge? High appreciate for
> your check and feedback.
> 
> This series has seen so many revisions (often numbered the same, and while
> I was writting this reply, here is a new revision) in the last days that I 
> put it at
> the end of my queue simply to wait for a stable state.
> 
> By the way, simply pinging me to get your patches merged is easy, but if you
> care about the dpdk project, there are other series that need reviews/checks
> when merging, you are welcome to review and test patches.

Really sorry to bring you so many trouble, apart from ASan implementation 
patch, also have other error build, doc... patches, recently receive some 
comments from other domain experts and maintainers.
We are active to deal with them and have so many revisions. For the same 
numbers, it is our fault, sorry for that, and thanks a lot for your and 
reviewers' great support. 
Today we will send v13 version, and all the fix will be in this version. 
We also care about the quality, make sure to run cross-compilation build and 
unit test passed on our platforms then send the patch.
Hope that everything is well and could meet the expectation,  thanks a lot. 

> 
> 
> --
> David Marchand

Reply via email to