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 BDC559E7 for ; Tue, 14 Feb 2017 16:51:06 +0100 (CET) Received: by mail-wm0-f41.google.com with SMTP id r141so20621598wmg.1 for ; Tue, 14 Feb 2017 07:51:06 -0800 (PST) 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=F0PsN5F9xjaPwnHowe02xueapeZTHIjfwXdgnIE2zyM=; b=m6EP/GfOePfX9b1L7RnLJIowI2Pu1mGBTpa4KrDBHf58XteR5EXvTyIbyMDiRg1Zh2 RAgveCvckb68Wf49gWPkGV6QiMpQMjj45ijp8szVUNh2OUajAThNHA2w6wIc6AQhw961 VjCQTFVUc5LGctakLwvzlTP65PQ2/tjRWW4s3tTnILZZGDzKzJI2dRFXU4jNacoXpatV cWl1fQXex7INfjoW4QuY7kW47bQT6+M6WEpbxSmluq2iKs67DkwOX3k9pLVel6nt4pkI mZj/Gj1wLYksV75P58vTCCloAsXdkfwFSeXI6/vaMiBKHt+Za0OkqotgCq64D73b50YK Rukg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=F0PsN5F9xjaPwnHowe02xueapeZTHIjfwXdgnIE2zyM=; b=SCHHSfhDeU2vHRNNMQR9kXgWtviliJIKguD6UbzgwxRGiFZV/ExuhxwXbayS4S77Nc gLU+9aDk8n9OuZqC3sWP0T8GXAfYi0JFQugfEES56Gn/qi9ZNX2lW1pF9sg+rbaYcL7N HFiSzCyjTDXHNoqiODmxtI+50Be+mSTxTZb7pN2bm7EiJU7xPkaUXghJabG32/qgrSox Cx0Nvqtz32kuUdWEA0lc75ThWcGA38CNjK3E8bg8bEjFFUh0fuo1uCWS0T/O5m1x2fkZ WoUa1D93uiThjW3fa6nEfiKyuNR15Crm6FOK6IvzWlPwSrKBcYvj4HqePaIDv2btTDkj ckzA== X-Gm-Message-State: AMke39l5cF8KPaqM5dG/pz+89zkVjgCbFRKTEs6sde/+POXUl83hNjIVElnhFL9+iR2FF9J9 X-Received: by 10.28.212.84 with SMTP id l81mr4166378wmg.119.1487087466506; Tue, 14 Feb 2017 07:51:06 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id b87sm1788118wmi.0.2017.02.14.07.51.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 07:51:05 -0800 (PST) From: Thomas Monjalon To: John McNamara Cc: dev@dpdk.org Date: Tue, 14 Feb 2017 16:51:05 +0100 Message-ID: <1551253.KADGnDBYIu@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1487086372-11630-1-git-send-email-john.mcnamara@intel.com> References: <1487086372-11630-1-git-send-email-john.mcnamara@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 17.02 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2017 15:51:07 -0000 2017-02-14 15:32, John McNamara: > -Resolved Issues > ---------------- > - > -.. This section should contain bug fixes added to the relevant sections. Sample format: > - > - * **code/section Fixed issue in the past tense with a full stop.** > - > - Add a short 1-2 sentence description of the resolved issue in the past tense. > - The title should contain the code/lib section like a commit message. > - Add the entries in alphabetic order in the relevant sections below. > - > - This section is a comment. do not overwrite or remove it. > - Also, make sure to start the actual text at the margin. > - ========================================================= > - > - > -EAL > -~~~ > - > > Drivers > ~~~~~~~ > > * **net/virtio: Fixed multiple process support.** > > - Fixed few regressions introduced in recent releases that break the virtio > + Fixed a few regressions introduced in recent releases that break the virtio > multiple process support. > > > -Libraries > -~~~~~~~~~ > - > - > Examples > ~~~~~~~~ > > * **examples/ethtool: Fixed crash with non-PCI devices.** > > - Querying a non-PCI device was dereferencing non-existent PCI data > - resulting in a segmentation fault. > + Fixed issue where querying a non-PCI device was dereferencing non-existent > + PCI data resulting in a segmentation fault. It looks strange to remove the "Resolved Issues" heading while keeping content. I think we could totally remove them as most of the fixes are not documented here anyway.