From: Axel Lin <axel.lin@gmail.com>
To: linux-mmc@vger.kernel.org
Cc: Sangwook Lee <sangwook.lee@samsung.com>, Chris Ball <cjb@laptop.org>
Subject: [linux-next] sdhci-s3c build error
Date: Sun, 04 Dec 2011 08:04:05 +0800 [thread overview]
Message-ID: <1322957045.19303.0.camel@phoenix> (raw)
commit 666b6ab "mmc: sdhci-s3c: Add pm_caps into SD/MMC host" introduces below
build error:
CC drivers/mmc/host/sdhci-s3c.o
drivers/mmc/host/sdhci-s3c.c: In function 'sdhci_s3c_probe':
drivers/mmc/host/sdhci-s3c.c:524: error: 'struct s3c_sdhci_platdata' has no member named 'pm_caps'
drivers/mmc/host/sdhci-s3c.c:525: error: 'struct s3c_sdhci_platdata' has no member named 'pm_caps'
make[3]: *** [drivers/mmc/host/sdhci-s3c.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
Forgot to add pm_caps to struct s3c_sdhci_platdata?
Regards,
Axel
next reply other threads:[~2011-12-04 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 0:04 Axel Lin [this message]
2011-12-04 0:09 ` [linux-next] sdhci-s3c build error Chris Ball
2011-12-08 3:52 ` 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=1322957045.19303.0.camel@phoenix \
--to=axel.lin@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sangwook.lee@samsung.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