linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: spi-devel-general@lists.sourceforge.net,
	linux-mmc@vger.kernel.org, Ernst Schwab <eschwab@online.de>,
	Antonio Ospite <ospite@studenti.unina.it>,
	Ned Forrester <nforrester@whoi.edu>,
Subject: Request for SPI testing
Date: Tue, 29 Jun 2010 21:30:34 -0600	[thread overview]
Message-ID: <AANLkTimVajsJq9lRSLbv8_lzu7g_CL5ptmV5OLG6dBds@mail.gmail.com> (raw)

I've pushed out Ernst's spi bus locking API patches to the following
branch.  Before I push them into linux-next, I'd like to get some
testing.  Can I have some volunteers please to pull this branch and
give it a spin?  Bonus points for people who have mmc cards
multiplexed with other devices on their SPI bus.

Cheers,
g.

The following changes since commit 5904b3b81d25166e5e39b9727645bb47937618e3:
  Linus Torvalds (1):
        Merge branch 'perf-fixes-for-linus' of
git://git.kernel.org/.../tip/linux-2.6-tip

are available in the git repository at:

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

Cory Maccarrone (1):
      SPI100k: Fix 8-bit and RX-only transfers

Ernst Schwab (2):
      spi/mmc_spi: SPI bus locking API, using mutex
      spi/mmc_spi: mmc_spi adaptations for SPI bus locking API

 drivers/mmc/host/mmc_spi.c  |   59 ++---------
 drivers/spi/omap_spi_100k.c |   23 +++--
 drivers/spi/spi.c           |  225 ++++++++++++++++++++++++++++++++++++-------
 include/linux/spi/spi.h     |   12 +++
 4 files changed, 227 insertions(+), 92 deletions(-)

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

             reply	other threads:[~2010-06-30  3:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30  3:30 Grant Likely [this message]
2010-06-30 11:57 ` Request for SPI testing Matt Fleming
2010-06-30 12:44 ` Ernst Schwab
2010-07-03 17:05 ` Antonio Ospite
2010-07-04  4:51   ` Grant Likely

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=AANLkTimVajsJq9lRSLbv8_lzu7g_CL5ptmV5OLG6dBds@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=eschwab@online.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nforrester@whoi.edu \
    --cc=ospite@studenti.unina.it \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).