From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Axel Lin <axel.lin@ingics.com>,
Mike Rapoport <mike@compulab.co.il>,
Laxman Dewangan <ldewangan@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: tps6586x: Having slew rate settings for other than SM0/1 is not fatal
Date: Tue, 19 Feb 2013 20:07:04 +0000 [thread overview]
Message-ID: <20130219200703.GE23508@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5123D362.4000702@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
On Tue, Feb 19, 2013 at 12:32:50PM -0700, Stephen Warren wrote:
> On 02/19/2013 11:26 AM, Mark Brown wrote:
> > - what he's saying is that the error handling here seems
> > excessive.
> Why shouldn't the driver return an error if it's asked to do something
> that's impossible?
I'm having a hard time caring too much to be honest. On the one hand it
means that if that feature gets added for some reason new DTs won't work
on older kernels, on the other hand perhaps the hardware doesn't support
doing this at all.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-19 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 11:50 [PATCH] regulator: tps6586x: Having slew rate settings for other than SM0/1 is not fatal Axel Lin
2013-02-19 16:47 ` Stephen Warren
2013-02-19 18:26 ` Mark Brown
2013-02-19 19:32 ` Stephen Warren
2013-02-19 20:07 ` Mark Brown [this message]
2013-02-20 0:53 ` Axel Lin
2013-02-20 2:12 ` Stephen Warren
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=20130219200703.GE23508@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@ingics.com \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=swarren@wwwdotorg.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 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.