public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Greg KH <greg@kroah.com>, Grant Likely <grant@secretlab.ca>,
	Jean Delvare <khali@linux-fr.org>,
	Ben Dooks <ben-linux@fluff.org>,
	Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Samuel Oritz <sameo@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] regmap: Add SPI bus support
Date: Wed, 20 Jul 2011 11:33:13 +0100	[thread overview]
Message-ID: <20110720103312.GA30059@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110719215120.GS6848@ponder.secretlab.ca>

On Tue, Jul 19, 2011 at 03:51:20PM -0600, Grant Likely wrote:

> regmap_init_i2c/spi should take an i2c_client and spi_device pointer
> respectively so it can be type checked.

Bah, you're right.  That was me trying to do the update far too quickly.
Fixed now, thanks for spotting.  Though I still don't find this
interface so pleasant to use with the multi-bus devices.

  reply	other threads:[~2011-07-20 10:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 10:04 [PATCH 0/4] regmap: Generic I2C and SPI register map library Mark Brown
2011-07-18 10:07 ` [PATCH 1/4] regmap: Add generic non-memory mapped register access API Mark Brown
2011-07-18 10:07   ` [PATCH 2/4] regmap: Add I2C bus support Mark Brown
2011-07-18 10:07   ` [PATCH 3/4] regmap: Add SPI " Mark Brown
2011-07-19 21:51     ` Grant Likely
2011-07-20 10:33       ` Mark Brown [this message]
2011-07-18 10:07   ` [PATCH 4/4] regulator: Convert tps65023 to use regmap API Mark Brown
2011-07-18 10:38   ` [PATCH 1/4] regmap: Add generic non-memory mapped register access API Takashi Iwai
2011-07-18 10:50     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2011-07-16  2:48 [PATCH 0/4] regmap: Generic I2C and SPI register map library Mark Brown
2011-07-16  2:48 ` [PATCH 1/4] regmap: Add generic non-memory mapped register access API Mark Brown
2011-07-16  2:48   ` [PATCH 3/4] regmap: Add SPI bus support Mark Brown
2011-07-15  6:22 [PATCH 0/4] regmap: Generic I2C and SPI register map library Mark Brown
2011-07-15  6:23 ` [PATCH 1/4] regmap: Add generic non-memory mapped register access API Mark Brown
2011-07-15  6:23   ` [PATCH 3/4] regmap: Add SPI bus support Mark Brown
2011-07-09  4:49 [PATCH 0/4] regmap: Generic I2C and SPI register map library Mark Brown
2011-07-09  4:50 ` [PATCH 1/4] regmap: Add generic non-memory mapped register access API Mark Brown
2011-07-09  4:50   ` [PATCH 3/4] regmap: Add SPI bus support Mark Brown
2011-07-15  2:53     ` Grant Likely
2011-07-15  4:39       ` Mark Brown
2011-07-15  5:04         ` Grant Likely
2011-07-15  5:09           ` Mark Brown
2011-07-15  9:01             ` Jonathan Cameron
2011-07-15 18:30               ` 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=20110720103312.GA30059@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ben-linux@fluff.org \
    --cc=dp@opensource.wolfsonmicro.com \
    --cc=grant.likely@secretlab.ca \
    --cc=grant@secretlab.ca \
    --cc=greg@kroah.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.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