Soft Patch Panel
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ogawa.yasufumi@lab.ntt.co.jp, spp@dpdk.org
Subject: Re: [spp] [PATCH] version: 18.02-rc3
Date: Thu, 8 Feb 2018 15:31:20 +0000	[thread overview]
Message-ID: <4d2fa69b-cbcc-92bc-3f21-7113e6f6d50c@intel.com> (raw)
In-Reply-To: <1518103102-4679-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>

On 2/8/2018 3:18 PM, ogawa.yasufumi@lab.ntt.co.jp wrote:
> From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> 
> Fix compile error for updating v18.02. This version of SPP is checked
> for compile with DPDK 18.02-rc3.
> 
> Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
> ---
>  Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Makefile b/Makefile
> index abef16b..e659798 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -29,7 +29,7 @@
>  #   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>  #   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>  
> -VERSION = 17.11
> +VERSION = 18.02-rc3

Hi Yasufumi,

I think it is not required to version for DPDK -rcX releases.
We can do this when v18.02 released, which is a few days away.

But I believe it makes sense to fix build errors seen against dpdk master, and
for this specific case it can be fixed in a way that works fine with both v17.11
and dpdk master.

>  
>  ifeq ($(RTE_SDK),)
>  $(error "Please define RTE_SDK environment variable")
> 

  reply	other threads:[~2018-02-08 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 15:18 ogawa.yasufumi
2018-02-08 15:31 ` Ferruh Yigit [this message]
2018-02-09  2:04   ` Yasufumi Ogawa

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=4d2fa69b-cbcc-92bc-3f21-7113e6f6d50c@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@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 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).