From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mfd: arizona: Add DT/ACPI u32 helper functions
Date: Wed, 27 May 2015 11:08:31 +0100 [thread overview]
Message-ID: <20150527100831.GE31187@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150527092440.GB11677@x1>
On Wed, May 27, 2015 at 10:24:40AM +0100, Lee Jones wrote:
> On Mon, 25 May 2015, Charles Keepax wrote:
>
> > Add helpers to read u32's and arrays of u32's from device tree or ACPI
> > using the new device properties API.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> > drivers/mfd/arizona-core.c | 39 ++++++++++++++++++++++++++++++++++++++
> > include/linux/mfd/arizona/core.h | 5 ++++
> > 2 files changed, 44 insertions(+), 0 deletions(-)
>
> Me no likey!
>
> There are 100's of 'required' and 'optional' properties in the kernel
> and it's normally the decision to early return or not that seals the
> fate of a given driver. I'm not happy for platforms to start adding
> their own variants.
>
> If you really do think these kinds of "helpers" add value, then make
> them generic, so everyone can make use of them. Personally, I'm
> dubious however.
Thats cool I don't really have any problem with dropping this
patch and doing the necessary checking where appropriate.
Thanks,
Charles
next prev parent reply other threads:[~2015-05-27 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 9:28 [PATCH 1/2] mfd: arizona: Add convience defines for micd_rate/micd_bias_starttime Charles Keepax
2015-05-25 9:28 ` [PATCH 2/2] mfd: arizona: Add DT/ACPI u32 helper functions Charles Keepax
2015-05-27 9:24 ` Lee Jones
2015-05-27 10:08 ` Charles Keepax [this message]
2015-05-27 9:18 ` [PATCH 1/2] mfd: arizona: Add convience defines for micd_rate/micd_bias_starttime Lee Jones
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=20150527100831.GE31187@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox