From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sangbeom Kim <sbkim73@samsung.com>
Cc: "'Axel Lin'" <axel.lin@gmail.com>,
linux-kernel@vger.kernel.org, "'Liam Girdwood'" <lrg@ti.com>
Subject: Re: [PATCH 1/2] regulator: s5m8767: Add missing breaks
Date: Thu, 12 Jan 2012 00:40:44 -0800 [thread overview]
Message-ID: <20120112084043.GC1176@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <027001ccd104$47bdb0b0$d7391210$@com>
On Thu, Jan 12, 2012 at 05:29:19PM +0900, Sangbeom Kim wrote:
> During normal test, I can't detect the problem.
> But It should add break to apply proper ramp slope.
Looking at the code you're unlikely to see a problem as the failure will
be to ramp more slowly which will just reduce performance rather than
cause crashes or anything like ramping too quickly can.
next prev parent reply other threads:[~2012-01-12 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 6:57 [PATCH 1/2] regulator: s5m8767: Add missing breaks Axel Lin
2012-01-12 6:58 ` [PATCH 2/2] regulator: s5m8767: Remove redundant MODULE_ALIAS Axel Lin
2012-01-12 8:36 ` Sangbeom Kim
2012-01-12 8:29 ` [PATCH 1/2] regulator: s5m8767: Add missing breaks Sangbeom Kim
2012-01-12 8:40 ` Mark Brown [this message]
2012-01-12 8:42 ` Mark Brown
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=20120112084043.GC1176@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sbkim73@samsung.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