From: Thomas Monjalon <thomas@monjalon.net>
To: Marcin Smoczynski <marcinx.smoczynski@intel.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: fix Makefile indentation
Date: Thu, 09 May 2019 22:39:22 +0200 [thread overview]
Message-ID: <5233178.WEQSE2tF2f@xps> (raw)
Message-ID: <20190509203922.cr7RGXaux0T2zqGyZuUoUXX4MZ9H645UIidF9NWJ-LM@z> (raw)
In-Reply-To: <20190508130956.3532-1-marcinx.smoczynski@intel.com>
08/05/2019 15:09, Marcin Smoczynski:
> Fix invalid indentation - extra whitespace before error directive which
> is causing syntax error when no pkgconfig file for the DPDK is found and
> RTE_SDK is not specified.
>
> Signed-off-by: Marcin Smoczynski <marcinx.smoczynski@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-09 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 13:09 Marcin Smoczynski
2019-05-08 13:09 ` Marcin Smoczynski
2019-05-09 20:39 ` Thomas Monjalon [this message]
2019-05-09 20:39 ` 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=5233178.WEQSE2tF2f@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=marcinx.smoczynski@intel.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).