DPDK patches and discussions
 help / color / mirror / Atom feed
From: Clemens Famulla-Conrad <cfamullaconrad@suse.com>
To: paul.szczepanek@arm.com
Cc: nd@arm.com, dev@dpdk.org
Subject: Re: [PATCH v2] dts: fix deterministic doc
Date: Mon, 16 Jun 2025 10:23:50 +0200	[thread overview]
Message-ID: <4c07ffc166d99607736e0396ea01e8264406bd26.camel@suse.com> (raw)
In-Reply-To: <20250611140530.51551-1-cfamullaconrad@suse.com>

> Thanks. This needs to pass the linter, see my suggestions below.

Thanks for your suggestions!

The CI is still failing[1] in "Windows Server 2022" =>
dpdk_msvc_compile
I don't see a relation to my change and also other patches show the
same issue[2]. Not sure if I need to do something, do you have an
advice?

[1] http://mails.dpdk.org/archives/test-report/2025-June/885350.html
[2] http://mails.dpdk.org/archives/test-report/2025-June/885280.html

  reply	other threads:[~2025-06-16  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  9:35 [PATCH 1/1] " Clemens Famulla-Conrad
2025-06-09  9:12 ` Paul Szczepanek
2025-06-11 14:05   ` [PATCH v2] " Clemens Famulla-Conrad
2025-06-16  8:23     ` Clemens Famulla-Conrad [this message]
2025-06-16 16:17     ` Luca Vizzarro

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=4c07ffc166d99607736e0396ea01e8264406bd26.camel@suse.com \
    --to=cfamullaconrad@suse.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=paul.szczepanek@arm.com \
    /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).