From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id A6D732BA5 for ; Thu, 27 Oct 2016 14:16:54 +0200 (CEST) Received: by mail-wm0-f41.google.com with SMTP id 140so23610406wmv.0 for ; Thu, 27 Oct 2016 05:16:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=oiv4bfiH5YjMfunR9fP0qFnbwM7egoByyptA2p5+H4Q=; b=CuiuSnEPiQihP+JrbgCbMZvUsDzXUXYN0KpgmXm/Di1Conv7vW8iYE8E9+UwISFRLb k9BpWO77mHna6ERMctUeJCG5uTIkr9cOrecdlx6aHJGZpBybXocHxNnLBEA0XbCR1SwZ lRuiExabCMY6aZHuehaX+ptM0J6EjR4dRTyPTNHwi7383bRKrvMpDnom74//JVbw77ku 2r77/3zlXxecACI3LYCVDy33WeABg9LiXZAzGjGHF7gYcBn9QWPwtUVxQt/esfaow1dy vMHbTcIo0uGIkmrG9BFMoTq9v2dGH6SrQZ1oEakTITy3GkplenqFYh2GkR0bsrd0UMUd +zXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=oiv4bfiH5YjMfunR9fP0qFnbwM7egoByyptA2p5+H4Q=; b=eUtGDeEAQIc9wu34K8WH3XjZzaRmnf7yXkKKJb9g7Kp/9kz6DeiA1+K4QG9UNH0mhi IT+MyH8kEOE/5qp7sqKCJI0DGNFtWNvq99ctRgatqG41k8Iqcp5UF5V5iTT7B6rwK8T3 VGB0ujzkWIhdVHpbuqECAeiiHnl/kd4VrQwkPQ2pZNq1VO1hRj/ekyqR6RC+5yVSjt45 kDexrW3qic3ApakBD5OByOcFnK1gikLVhMn7YAI3+QBe4FFPv7y06H0eu16R5UiXFPau aDbzv/73psHWD+jidE5mq6OEipIFs1v4zmSlHJP5SWiVWNhNKsAettzUR/GYIVGNU3fB bKVA== X-Gm-Message-State: ABUngve/c8vLwMC1gCWXHuPGqSEiKO0h5fTEDSSTOsax4xotk+EFGW+Vuqy78ek1Ds7P7L9+ X-Received: by 10.28.183.213 with SMTP id h204mr12763518wmf.87.1477570605909; Thu, 27 Oct 2016 05:16:45 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id f17sm2960342wmf.10.2016.10.27.05.16.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Oct 2016 05:16:45 -0700 (PDT) From: Thomas Monjalon To: Shreyansh Jain Date: Thu, 27 Oct 2016 14:16:44 +0200 Message-ID: <2687270.6CHbVYPQ99@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <9eb3805d-8f6c-c1ec-4be6-35452a3d8458@nxp.com> References: <1477552109-18624-1-git-send-email-shreyansh.jain@nxp.com> <1477567752-23039-1-git-send-email-shreyansh.jain@nxp.com> <9eb3805d-8f6c-c1ec-4be6-35452a3d8458@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org, ferruh.yigit@intel.com Subject: Re: [dpdk-dev] [PATCH v4] eal: fix lib version for device generalization patches X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2016 12:16:54 -0000 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.