dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 0/2] enable dmadev lib to be compiled with MSVC
Date: Mon, 9 Dec 2024 09:53:51 +0800	[thread overview]
Message-ID: <2f7fa532-e70a-4f83-ab6f-de40a40356a6@huawei.com> (raw)
In-Reply-To: <1733513273-25550-1-git-send-email-andremue@linux.microsoft.com>

Series-acked-by: Chengwen Feng <fengchengwen@huawei.com>

Thanks

On 2024/12/7 3:27, Andre Muezerie wrote:
> The first patch eliminates undefined behavior in the dmadev lib:
> 
> lib\dmadev\rte_dmadev_trace_fp.h(36):
>     warning C5101: use of preprocessor directive in
>     function-like macro argument list is undefined behavior
> 
> The second patch enables the dmadev library to be compiled with MSVC.
> 
> Andre Muezerie (2):
>   lib/dmadev: eliminate undefined behavior
>   lib/dmadev: enable dmadev lib to be compiled with MSVC
> 
>  lib/dmadev/meson.build           |  6 ----
>  lib/dmadev/rte_dmadev_trace.h    | 62 ++++++++++++++++++++++++++++----
>  lib/dmadev/rte_dmadev_trace_fp.h | 52 +++++++++++++++++++++++----
>  3 files changed, 102 insertions(+), 18 deletions(-)
> 
> --
> 2.47.0.vfs.0.3
> 


      parent reply	other threads:[~2024-12-09  1:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 19:27 [PATCH 0/2] enable dmadev lib to be compiled with MSVC Andre Muezerie
2024-12-06 19:27 ` [PATCH 1/2] lib/dmadev: eliminate undefined behavior Andre Muezerie
2024-12-09 12:58   ` Bruce Richardson
2024-12-09 23:21     ` [EXTERNAL] " Jerin Jacob
2024-12-10  0:58       ` fengchengwen
2025-01-24 11:13         ` David Marchand
2025-01-30 15:00           ` David Marchand
2024-12-06 19:27 ` [PATCH 2/2] lib/dmadev: enable dmadev lib to be compiled with MSVC Andre Muezerie
2024-12-09  1:53 ` fengchengwen [this message]

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=2f7fa532-e70a-4f83-ab6f-de40a40356a6@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=andremue@linux.microsoft.com \
    --cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).