From: Laxman Dewangan <ldewangan@nvidia.com>
To: Lee Jones <lee.jones@linaro.org>
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, 9 Mar 2016 18:52:58 +0530 [thread overview]
Message-ID: <56E023B2.5020207@nvidia.com> (raw)
In-Reply-To: <20160302130828.GB3444@x1>
Hi Lee,
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.
next prev parent reply other threads:[~2016-03-09 13:36 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 [this message]
2016-03-11 8:39 ` Lee Jones
2016-03-11 8:57 ` Laxman Dewangan
2016-03-16 8:42 ` Lee Jones
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=56E023B2.5020207@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=lee.jones@linaro.org \
--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 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.