From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com
Subject: Re: [PATCH v4] eal: fix lib version for device generalization patches
Date: Thu, 27 Oct 2016 14:16:44 +0200 [thread overview]
Message-ID: <2687270.6CHbVYPQ99@xps13> (raw)
In-Reply-To: <9eb3805d-8f6c-c1ec-4be6-35452a3d8458@nxp.com>
2016-10-27 17:02, Shreyansh Jain:
> Even though I have sent the v4, there is another possibility of
> splitting this log across API and ABI changes.
> Problem is that most of the changes are quite related in terms of impact
> on ABI and API. (some like rte_device is clear enough, though).
> Any suggestions? Would repetitions be OK in release notes?
In general, API change implies ABI change.
I think we must use the "ABI changes" section for cases where API is not changed.
No need of repeating in both sections.
next prev parent reply other threads:[~2016-10-27 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:38 [PATCH] eal: fix libabi macro for device generalization patches Shreyansh Jain
2016-10-26 13:00 ` [PATCH v2] " Shreyansh Jain
2016-10-26 13:12 ` Shreyansh Jain
2016-10-26 14:25 ` Ferruh Yigit
2016-10-26 15:23 ` Thomas Monjalon
2016-10-27 5:07 ` Shreyansh Jain
2016-10-27 5:06 ` Shreyansh Jain
2016-10-27 7:08 ` [PATCH v3] " Shreyansh Jain
2016-10-27 10:15 ` Thomas Monjalon
2016-10-27 11:10 ` Shreyansh Jain
2016-10-27 11:29 ` [PATCH v4] eal: fix lib version " Shreyansh Jain
2016-10-27 11:32 ` Shreyansh Jain
2016-10-27 12:16 ` Thomas Monjalon [this message]
2016-11-06 17:51 ` Thomas Monjalon
2016-10-26 13:02 ` [PATCH] eal: fix libabi macro " Shreyansh Jain
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=2687270.6CHbVYPQ99@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shreyansh.jain@nxp.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 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.