All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 5/5] mfd: arizona: Sync regcache after reset
Date: Tue, 20 Nov 2012 14:48:27 +0900	[thread overview]
Message-ID: <20121120054825.GA10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1353386781-10468-5-git-send-email-broonie@opensource.wolfsonmicro.com>

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

On Tue, Nov 20, 2012 at 01:46:21PM +0900, Mark Brown wrote:

> +		ret = regcache_sync(arizona->regmap);
> +		if (ret != 0) {
> +			dev_err(dev, "Failed to sync device: %d\n", ret);
> +			goto err_ldoena;

This should be err_reset - the change appears to have been originally
posted based on older code, not upstream.  I'll post a fixed patch
shortly and have rebuilt the tag so pulling should work.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-20  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  4:45 [PATCH 0/5] mfd: arizona: Updates for v3.7 Mark Brown
2012-11-20  4:46 ` [PATCH 1/5] mfd: wm5102: Update register patch for latest evaluation Mark Brown
2012-11-20  4:46   ` [PATCH 2/5] mfd: wm5110: Disable control interface error report for WM5110 rev B Mark Brown
2012-11-20  4:46   ` [PATCH 3/5] mfd: arizona: Use correct array for ARRAY_SIZE in mfd_add_devices call Mark Brown
2012-11-20  4:46   ` [PATCH 4/5] mfd: arizona: Correctly report when AIF2/AIF1 is underclocked Mark Brown
2012-11-20  4:46   ` [PATCH 5/5] mfd: arizona: Sync regcache after reset Mark Brown
2012-11-20  5:48     ` Mark Brown [this message]
2012-11-20  5:49     ` [PATCH] " Mark Brown
2012-11-20 11:47 ` [PATCH 0/5] mfd: arizona: Updates for v3.7 Samuel Ortiz

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=20121120054825.GA10560@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.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 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.