From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] ixgbe: Out-by-one in get/set EEPROM Date: Wed, 16 Sep 2015 15:23:39 +0200 Message-ID: <1735667.JZ2y0EAyYG@xps13> References: <1442408865-7569-1-git-send-email-remy.horton@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Remy Horton Return-path: Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by dpdk.org (Postfix) with ESMTP id AB45C377E for ; Wed, 16 Sep 2015 15:24:47 +0200 (CEST) Received: by wiclk2 with SMTP id lk2so73082462wic.0 for ; Wed, 16 Sep 2015 06:24:47 -0700 (PDT) In-Reply-To: <1442408865-7569-1-git-send-email-remy.horton@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2015-09-16 14:07, Remy Horton: > Incorrect operator in ixgbe_get_eeprom & ixgbe_set_eeprom prevents > last byte of EEPROM being read/written, and hence cannot be dumped > or updated in entirity using these functions. This explanation is good but the title is not clear enough. It should start with "ixgbe: fix". Fix what? I'd say "fix access to last byte of EEPROM". Then creating a commit starting with "fix" should trigger 2 other things: - a Fixes: tag - an update in the release notes (because the bug exists in previous releases) Thanks