Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] regulator: s2mps11: Fix dwmmc failure on Gear 2
Date: Thu, 11 Dec 2014 13:13:05 +0000	[thread overview]
Message-ID: <20141211131305.GW11764@sirena.org.uk> (raw)
In-Reply-To: <1418301551-31678-1-git-send-email-k.kozlowski@samsung.com>

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

On Thu, Dec 11, 2014 at 01:39:11PM +0100, Krzysztof Kozlowski wrote:
> Invalid buck4 configuration in S2MPS14 regulators caused boot failure on
> Gear 2 (dwmmc_exynos):

What is invalid about the configuration and how is this change intended
to fix it?

> [    3.569137] EXT4-fs (mmcblk0p15): mounted filesystem with ordered data mode. Opts: (null)
> [    3.571716] VFS: Mounted root (ext4 filesystem) readonly on device 179:15.
> [    3.580836] devtmpfs: mounted
> [    3.582033] Freeing unused kernel memory: 284K (c05b4000 - c05fb000)
> [    3.629842] mmcblk0: error -110 sending status command, retrying
> [    3.630244] mmcblk0: error -110 sending status command, retrying

Please don't include large log sections in commit messages, edit them
down to any relevant information.  They get very large and obscure the
relevant content in the messages.

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

  reply	other threads:[~2014-12-11 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 12:39 [PATCH] regulator: s2mps11: Fix dwmmc failure on Gear 2 Krzysztof Kozlowski
2014-12-11 13:13 ` Mark Brown [this message]
2014-12-11 13:20   ` Krzysztof Kozlowski

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=20141211131305.GW11764@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbkim73@samsung.com \
    --cc=stable@vger.kernel.org \
    /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