From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Horton, Remy" <remy.horton@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] ixgbe: fix access to last byte of EEPROM
Date: Wed, 28 Oct 2015 17:15:31 +0100 [thread overview]
Message-ID: <1931708.rTC1bdOP3C@xps13> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836A9892B@irsmsx105.ger.corp.intel.com>
> > 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.
> >
> > Fixes: 0198848a47f5 ("ixgbe: add access to specific device info")
> >
> > Signed-off-by: Remy Horton <remy.horton@intel.com>
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-10-28 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 13:07 [dpdk-dev] [PATCH] ixgbe: Out-by-one in get/set EEPROM Remy Horton
2015-09-16 13:23 ` Thomas Monjalon
2015-09-17 9:05 ` [dpdk-dev] [PATCH v2] ixgbe: fix access to last byte of EEPROM Remy Horton
2015-09-17 10:13 ` Thomas Monjalon
2015-09-17 13:47 ` [dpdk-dev] [PATCH v3] " Remy Horton
2015-09-21 9:13 ` Ananyev, Konstantin
2015-10-28 16:15 ` 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=1931708.rTC1bdOP3C@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.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).