From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: thomas@monjalon.net, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ci: fix arm64 config filename
Date: Fri, 29 Mar 2019 12:14:54 -0400 [thread overview]
Message-ID: <f7tr2apk681.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <1553874938-31673-1-git-send-email-david.marchand@redhat.com> (David Marchand's message of "Fri, 29 Mar 2019 16:55:38 +0100")
David Marchand <david.marchand@redhat.com> writes:
> The ARM64 config file has been renamed in the commit
> ae2f2fee247a ("build: rename linuxapp to linux in meson cross files").
>
> Fixes: 99889bd85228 ("ci: introduce Travis builds for GitHub repositories")
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
Thanks for the fix - I'll drop it from my testing series.
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2019-03-29 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 15:55 David Marchand
2019-03-29 15:55 ` David Marchand
2019-03-29 16:14 ` Aaron Conole [this message]
2019-03-29 16:14 ` Aaron Conole
2019-03-29 23:02 ` Thomas Monjalon
2019-03-29 23:02 ` Thomas Monjalon
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=f7tr2apk681.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).