From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.23-git2 buid failure
Date: Sat, 13 Oct 2007 12:45:47 +0530 [thread overview]
Message-ID: <471070A3.6020003@linux.vnet.ibm.com> (raw)
Hi,
The 2.6.23-git2 build fails with build error
CC [M] drivers/mmc/core/core.o
CC [M] drivers/mmc/core/sysfs.o
CC [M] drivers/mmc/core/bus.o
CC [M] drivers/mmc/core/host.o
drivers/mmc/core/host.c: In function ‘mmc_remove_host’:
drivers/mmc/core/host.c:146: error: implicit declaration of function ‘led_trigger_unregister’
drivers/mmc/core/host.c:146: error: ‘struct mmc_host’ has no member named ‘led’
make[3]: *** [drivers/mmc/core/host.o] Error 1
make[2]: *** [drivers/mmc/core] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next reply other threads:[~2007-10-13 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 7:15 Kamalesh Babulal [this message]
2007-10-14 11:18 ` 2.6.23-git2 buid failure Ahmed S. Darwish
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=471070A3.6020003@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.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).