From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>,
fengguang.wu@intel.com, Steven Miao <realmz6@gmail.com>
Cc: adi-buildroot-devel@lists.sourceforge.net,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH] Documentation: fix blackfin gptimers-example build errors
Date: Fri, 16 Jan 2015 14:35:48 -0800 [thread overview]
Message-ID: <54B99244.8080404@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Don't build the blackfin gptimers-example module when BFIN_GPTIMERS
is not enabled. Allow the build when BFIN_GPTIMERS is =y or =m.
I believe that this patch fixes these build errors, but I don't
have a build environment to test this.
ERROR: "disable_gptimers" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "enable_gptimers" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "set_gptimer_config" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "clear_gptimer_intr" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "get_gptimer_period" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "get_gptimer_pwidth" [Documentation/blackfin/gptimers-example.ko] undefined!
ERROR: "get_gptimer_intr" [Documentation/blackfin/gptimers-example.ko] undefined!
Reported-by: Fenggaung Wu <fengguang.wu@intel.com>
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Documentation/blackfin/Makefile | 2 ++
1 file changed, 2 insertions(+)
--- lnx-319-rc4.orig/Documentation/blackfin/Makefile
+++ lnx-319-rc4/Documentation/blackfin/Makefile
@@ -1,3 +1,5 @@
ifneq ($(CONFIG_BLACKFIN),)
+ifneq ($(CONFIG_BFIN_GPTIMERS,)
obj-m := gptimers-example.o
endif
+endif
next reply other threads:[~2015-01-16 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 22:35 Randy Dunlap [this message]
2015-01-28 19:08 ` [PATCH] Documentation: fix blackfin gptimers-example build errors Jonathan Corbet
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=54B99244.8080404@infradead.org \
--to=rdunlap@infradead.org \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=corbet@lwn.net \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=realmz6@gmail.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