Messages in this thread | | | Date | Thu, 21 Feb 2013 10:36:38 -0700 | Subject | Re: ixgbe: fix possible data corruption in read_i2c_byte | From | Shuah Khan <> |
| |
On Wed, Feb 20, 2013 at 8:33 PM, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote: > Gitweb: http://git.kernel.org/linus/;a=commit;h=d0310dc415a670ae2b2e27076b4685d988830479 > Commit: d0310dc415a670ae2b2e27076b4685d988830479 > Parent: 4c696ca9fbabc5f94a3c6db7f009e73f0ef21831 > Author: Emil Tantilov <emil.s.tantilov@intel.com> > AuthorDate: Fri Jan 18 02:16:41 2013 +0000 > Committer: Jeff Kirsher <jeffrey.t.kirsher@intel.com> > CommitDate: Fri Feb 15 23:16:09 2013 -0800 > > ixgbe: fix possible data corruption in read_i2c_byte > > This patch makes sure that the SW lock is released after all i2c > operations complete in the retry code path. > > Signed-off-by: Emil Tantilov <emil.s.tantilov@intel.com> > Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Jeff,
Should this patch be considered for stable? This patch applied cleanly to 3.7 and 3.4. I haven't done any testing yet.
-- Shuah
| |