linux-kernel - [GIT PULL] spi driver bug fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACxGe6uPnXm4Ehk0Bwss_B48j3oUtE1L8SSTyCE6nC2b9K0hhA@mail.gmail.com>
Date:	Tue, 4 Oct 2011 10:14:41 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	spi-devel-general@...ts.sourceforge.net,
	Tomoya MORINAGA <morinaga526@....okisemi.com>,
	stable@...nel.org
Subject: [GIT PULL] spi driver bug fixes

Hi Linus,

Here are some bug fixes for the topcliff spi driver.

Tomoya, are these applicable for the stable tree?

The following changes since commit 0f86267b79bc6e357b8606077c7f70239045ea9c:

  Merge branch 'hwmon-for-linus' of git://github.com/groeck/linux
(2011-10-03 12:54:56 -0700)

are available in the git repository at:

  git://git.secretlab.ca/git/linux-2.6 spi/merge

Tomoya MORINAGA (5):
      spi-topcliff-pch: add tx-memory clear after complete transmitting
      spi-topcliff-pch: Fix SSN Control issue
      spi-topcliff-pch: Fix CPU read complete condition issue
      spi-topcliff-pch: Add recovery processing in case FIFO overrun
error occurs
      spi-topcliff-pch: Fix overrun issue

 drivers/spi/spi-topcliff-pch.c |   93 ++++++++++++++++++++++++++++------------
 1 files changed, 66 insertions(+), 27 deletions(-)


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/