From: Chris Ball <chris@printf.net>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Andreas Fenkart <afenkart@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, balajitk <balajitk@ti.com>
Subject: Re: [mmc:mmc-next 79/96] drivers/mmc/host/omap_hsmmc.c:1841:30: error: 'struct dev_pm_info' has no member named 'runtime_status'
Date: Thu, 22 May 2014 13:41:28 +0100 [thread overview]
Message-ID: <86oayqq93b.fsf@void.printf.net> (raw)
In-Reply-To: <CAPDyKFoWABO-k9dh5AvhaJFoF-NRCBz1_G+fJ53MPnzBr42CfQ@mail.gmail.com> (Ulf Hansson's message of "Thu, 22 May 2014 14:39:14 +0200")
Hi,
On Thu, May 22 2014, Ulf Hansson wrote:
> I had a second look at Andreas Fenkart's patchset to enable SDIO irq
> for omap. Those needs an additional iteration, since there are
> unresolved dependencies to CONFIG_PM_RUNTIME (and possibly to other
> Kconfigs as well). Apparently I had all the needed Kconfigs enabled
> while I compile tested them. :-(
>
> I tried out doing a local re-base, to remove the related omap patches.
> If you remove the patches below you won't get any conflicts for
> omap_hsmmc. Can you do that?
>
> Andreas:
> mmc: omap_hsmmc: Enable SDIO interrupt
> mmc: omap_hsmmc: enable wakeup event for sdio OMAP4
> mmc: omap_hsmmc: Extend debugfs by SDIO IRQ handling, runtime state
> mmc: omap_hsmmc: abort runtime suspend if pending sdio irq detected
> mmc: omap_hsmmc: switch default/idle pinctrl states in runtime hooks
> mmc: omap_hsmmc: Pin remux workaround to support SDIO interrupt on AM335x
>
> Balaji:
> mmc: omap_hsmmc: use IS_ERR macro for error checking
Done. Thanks!
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-05-22 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537de770.ItHqmb5BpaXWIlXq%fengguang.wu@intel.com>
2014-05-22 12:39 ` [mmc:mmc-next 79/96] drivers/mmc/host/omap_hsmmc.c:1841:30: error: 'struct dev_pm_info' has no member named 'runtime_status' Ulf Hansson
2014-05-22 12:41 ` Chris Ball [this message]
2014-05-22 14:24 ` Tony Lindgren
2014-05-23 8:19 ` Andreas Fenkart
2014-05-23 8:27 ` Balaji T K
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=86oayqq93b.fsf@void.printf.net \
--to=chris@printf.net \
--cc=afenkart@gmail.com \
--cc=balajitk@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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 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).