From: Andre Muezerie <andremue@linux.microsoft.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, konstantin.ananyev@huawei.com, thomas@monjalon.net,
ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
Cody Cheng <ccheng@iol.unh.edu>
Subject: Re: [PATCH v19 00/27] remove use of VLAs for Windows
Date: Tue, 4 Feb 2025 08:27:04 -0800 [thread overview]
Message-ID: <20250204162704.GA16594@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CAJvnSUASYqe39J3MTXqfEPSVWi6=z95TdN7z6e20QyJLeSNGug@mail.gmail.com>
On Tue, Feb 04, 2025 at 10:38:55AM -0500, Patrick Robb wrote:
> It looks like this failed the check-meson script which we incorporated into
> our apply/build pipeline recently, which is why this series got a "build
> failure." It is indicating there are issues with lib/vhost/meson.build
> and app/test/meson.build.
>
> Obviously we need to provide an email body which makes clear that
> check-meson was the source of the failure, and I have a UNH Lab ticket for
> this.
>
> Running Check Meson
> Error: Incorrect indent at app/test/meson.build:257
> Error: Incorrect indent at app/test/meson.build:258
> Error: Incorrect indent at lib/vhost/meson.build:23
> Error: Incorrect indent at lib/vhost/meson.build:24
Thanks for clarifying that Patrick.
I submitted v20 for this series fixing the errors above.
--
Andre Muezerie
prev parent reply other threads:[~2025-02-04 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1713397319-26135-1-git-send-email-roretzla@linux.microsoft.com>
[not found] ` <1738555590-12753-1-git-send-email-andremue@linux.microsoft.com>
2025-02-03 15:30 ` David Marchand
2025-02-04 15:38 ` Patrick Robb
2025-02-04 16:27 ` Andre Muezerie [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=20250204162704.GA16594@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=andremue@linux.microsoft.com \
--cc=aconole@redhat.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).