From: Rajendra Nayak <rnayak@ti.com>
To: balbi@ti.com
Cc: cjb@laptop.org, linux-omap@vger.kernel.org,
linux-mmc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
b-cousson@ti.com, Balaji TK <balajitk@ti.com>,
Rob Herring <rob.herring@calxeda.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] mmc: omap_hsmmc: Get rid of of_have_populated_dt() usage
Date: Wed, 11 Apr 2012 15:59:55 +0530 [thread overview]
Message-ID: <4F855D23.2090803@ti.com> (raw)
In-Reply-To: <20120411102632.GY12064@arwen.pp.htv.fi>
On Wednesday 11 April 2012 03:56 PM, Felipe Balbi wrote:
> On Wed, Apr 11, 2012 at 03:54:28PM +0530, Rajendra Nayak wrote:
>> On Wednesday 11 April 2012 03:39 PM, Felipe Balbi wrote:
>>> On Wed, Apr 11, 2012 at 03:33:13PM +0530, Rajendra Nayak wrote:
>>>> @@ -1564,7 +1564,7 @@ static void omap_hsmmc_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
>>>> * can't be allowed when booting with device
>>>> * tree.
>>>> */
>>>> - (!of_have_populated_dt())) {
>>>> + !host->dev->of_node) {
>>>
>>> won't compile
>>>
>> why? compiles fine for me.
>
> aren't you missing the opening parenthesis ? Or is there a something not
> shown in the context ?
>
Its the missing context thats confusing :-)
This is how the code looks in the file after the patch.
if ((OMAP_HSMMC_READ(host->base, HCTL) & SDVSDET) &&
(ios->vdd == DUAL_VOLT_OCR_BIT) &&
/*
* With pbias cell programming missing, this
* can't be allowed when booting with device
* tree.
*/
!host->dev->of_node) {
next prev parent reply other threads:[~2012-04-11 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:03 [PATCH] mmc: omap_hsmmc: Get rid of of_have_populated_dt() usage Rajendra Nayak
2012-04-11 10:09 ` Felipe Balbi
2012-04-11 10:24 ` Rajendra Nayak
2012-04-11 10:26 ` Felipe Balbi
2012-04-11 10:29 ` Rajendra Nayak [this message]
2012-04-11 10:31 ` Felipe Balbi
2012-04-11 12:10 ` Rob Herring
2012-04-11 14:05 ` T Krishnamoorthy, Balaji
2012-04-11 14:36 ` Chris Ball
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=4F855D23.2090803@ti.com \
--to=rnayak@ti.com \
--cc=b-cousson@ti.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rob.herring@calxeda.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.