DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Clemens Famulla-Conrad <cfamullaconrad@suse.com>
Cc: paul.szczepanek@arm.com, nd@arm.com, dev@dpdk.org
Subject: Re: [PATCH v2] dts: fix deterministic doc
Date: Thu, 19 Jun 2025 08:39:40 -0400	[thread overview]
Message-ID: <CAJvnSUCyfJJTjEpRQ8B0qL0MGrsUX2FRTzwuj14oUvnh5hHi+g@mail.gmail.com> (raw)
In-Reply-To: <4c07ffc166d99607736e0396ea01e8264406bd26.camel@suse.com>

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

Yes the windows failure was unrelated to your patch - sorry about the
noise.

Looks like Paul has applied this commit to next-dts.

On Mon, Jun 16, 2025 at 4:23 AM Clemens Famulla-Conrad <
cfamullaconrad@suse.com> wrote:

> > 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
>

[-- Attachment #2: Type: text/html, Size: 1310 bytes --]

  reply	other threads:[~2025-06-19 12:45 UTC|newest]

Thread overview: 6+ 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
2025-06-19 12:39       ` Patrick Robb [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=CAJvnSUCyfJJTjEpRQ8B0qL0MGrsUX2FRTzwuj14oUvnh5hHi+g@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=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).