All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache
Date: Mon, 10 Oct 2011 10:03:03 +0100	[thread overview]
Message-ID: <20111010090303.GC2563@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318167876-17801-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Sun, Oct 09, 2011 at 02:44:35PM +0100, Mark Brown wrote:
> If a register isn't cached then let callers know that so they can fall
> back or error handle appropriately.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  drivers/base/regmap/regcache-indexed.c |    7 +++----
>  drivers/base/regmap/regcache-lzo.c     |    4 ++--
>  drivers/base/regmap/regcache-rbtree.c  |    3 +--
>  drivers/base/regmap/regcache.c         |    2 +-
>  4 files changed, 7 insertions(+), 9 deletions(-)

Acked-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>

      parent reply	other threads:[~2011-10-10  9:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 13:44 [PATCH 1/2] regmap: Return a sensible error code if we fail to read the cache Mark Brown
2011-10-09 13:44 ` [PATCH 2/2] regmap: Allow caches for devices with no defaults Mark Brown
2011-10-09 17:43   ` Valdis.Kletnieks
2011-10-09 19:34     ` Mark Brown
2011-10-10  8:41   ` Dimitris Papastamos
2011-10-10  9:23     ` Mark Brown
2011-10-10 10:50       ` Dimitris Papastamos
2011-10-10  9:03 ` Dimitris Papastamos [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=20111010090303.GC2563@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.