From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, santosh.shukla@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH] eal: fix version map experimental export section
Date: Tue, 07 Nov 2017 00:07:07 +0100 [thread overview]
Message-ID: <2343504.OOURgLGTAf@xps> (raw)
In-Reply-To: <1508934589-161739-1-git-send-email-harry.van.haaren@intel.com>
25/10/2017 14:29, Harry van Haaren:
> Before this commit, the EXPERIMENTAL version of ABI
> derived from the DPDK_17.08 tag. In parallel there
> was a DPDK_17.11 tag.
>
> Experimental map should always derive from the latest ABI,
> so this patch moves the 17.11 section above EXPERIMENTAL,
> and updates EXPERIMENTAL to derive from the 17.11 map.
>
> Fixes: aadc3eb002d3 ("pci: export match function")
> Cc: santosh.shukla@caviumnetworks.com
>
> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
Rebased and applied, thanks
prev parent reply other threads:[~2017-11-06 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 12:29 Harry van Haaren
2017-11-06 23:07 ` 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=2343504.OOURgLGTAf@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=santosh.shukla@caviumnetworks.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).