From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Rhyland Klein <rklein@nvidia.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Fix MACRO for commonly declared MFD cell attributes
Date: Wed, 16 Mar 2016 08:42:19 +0000 [thread overview]
Message-ID: <20160316084219.GV13692@x1> (raw)
In-Reply-To: <56E2888D.3010406@nvidia.com>
On Fri, 11 Mar 2016, Laxman Dewangan wrote:
>
> On Friday 11 March 2016 02:09 PM, Lee Jones wrote:
> >On Wed, 09 Mar 2016, Laxman Dewangan wrote:
> >>On Wednesday 02 March 2016 06:38 PM, Lee Jones wrote:
> >>>On Mon, 29 Feb 2016, Laxman Dewangan wrote:
> >>>
> >>>>On Friday 26 February 2016 10:05 PM, Rhyland Klein wrote:
> >>>>>Did you not see warnings like this when you compiled the kernel? Did you
> >>>>>find a different approach than what I proposed above to deal with it?
> >>>>>I'd like to get this in soon so that when the max77620 drivers are all
> >>>>>in and using it, it should be functional.
> >>>>>
> >>>>I think the following change also crash in runtime:
> >>>>
> >>>>/***
> >>>>commit e60a946f05db2cac857025da6ffb72df48d3be54
> >>>>Author: Lee Jones <lee.jones@linaro.org>
> >>>>
> >>>> mfd: ab8500: Provide a small example using new MFD cell MACROs
> >>>>
> >>>>***/
> >>>>
> >>>>Should we have something MFD_CELL_RES, MFD_CELL_RES_PDATA,
> >>>>MFD_CELL_PDATA, for more common user and not to pass the NULL here.
> >>>I'll have a re-think about this.
> >>Did you get chance to look into this? Probably, I need to send my
> >>mfd series once this get fixed before that series applied.
> >Nothing is going to happen until v4.6 now. It's too late in the
> >release cycle to be making such a significant addition, and I'd like
> >the change to sit in -next for a good while before going in.
> >
> OK, so can I use the local initializations in my max77620 patches
> and resend?
> Then later we can have cleanups for part only?
>
> This is because if we get in next release then there is some other
> sub modules of the max77620 like clocks, watchdog, power etc which
> can go on their subsystem if common header is available.
>
> Sorry if I am asking too much..
For quick accptance, just submit using the normal un-MACRO'ed
structure.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-03-16 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:52 [PATCH] mfd: Fix MACRO for commonly declared MFD cell attributes Rhyland Klein
2016-02-19 8:50 ` Lee Jones
2016-02-19 16:28 ` Rhyland Klein
2016-02-26 16:35 ` Rhyland Klein
2016-02-29 12:38 ` Laxman Dewangan
2016-03-02 13:08 ` Lee Jones
2016-03-09 13:22 ` Laxman Dewangan
2016-03-11 8:39 ` Lee Jones
2016-03-11 8:57 ` Laxman Dewangan
2016-03-16 8:42 ` Lee Jones [this message]
2016-03-16 9:22 ` Laxman Dewangan
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=20160316084219.GV13692@x1 \
--to=lee.jones@linaro.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rklein@nvidia.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;
as well as URLs for NNTP newsgroup(s).