From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] build: fix incorrect variable name in error message
Date: Mon, 14 Jan 2019 12:05:18 +0100 [thread overview]
Message-ID: <2917550.LRSrnXiaZj@xps> (raw)
In-Reply-To: <1547125822.16085.3.camel@debian.org>
10/01/2019 14:10, Luca Boccassi:
> On Thu, 2019-01-10 at 10:29 +0000, Bruce Richardson wrote:
> > The variable name in the error message had an extra '_' which caused
> > an actual meson error when the message would otherwise be printed to
> > give meaningful information about what was going wrong.
> >
> > Fixes: 203b61dc5e18 ("build: improve error message for missing
> > dependency")
> > CC: stable@dpdk.org
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Acked-by: Luca Boccassi <bluca@debian.org>
Applied, thanks
prev parent reply other threads:[~2019-01-14 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 10:29 [PATCH] build: fix incorrect variable name in error message Bruce Richardson
2019-01-10 13:10 ` [dpdk-stable] " Luca Boccassi
2019-01-14 11:05 ` Thomas Monjalon [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=2917550.LRSrnXiaZj@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.