From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: devel@driverdev.osuosl.org, Greg KH <gregkh@suse.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [PATCH 3/3] staging/Makefile: Don't compile a media driver there
Date: Wed, 2 Nov 2011 09:45:08 -0200 [thread overview]
Message-ID: <20111102094508.5a4eded5@redhat.com> (raw)
In-Reply-To: <cover.1320233265.git.mchehab@redhat.com>
Otherwise, with driver as "y", compilation will break:
drivers/staging/media/as102/built-in.o: In function `as10x_cmd_get_demod_stats':
/home/v4l/work_trees/linux-next/drivers/staging/media/as102/as10x_cmd.c:306: multiple definition of `as10x_cmd_get_demod_stats'
drivers/staging/media/built-in.o:/home/v4l/work_trees/linux-next/drivers/staging/media/as102/as10x_cmd.c:306: first defined here
drivers/staging/media/as102/built-in.o:(.data+0x88): multiple definition of `as102_st_fw1'
drivers/staging/media/built-in.o:(.data+0x88): first defined here
as the same driver is already at staging/media/Makefile.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
index cf92bc1..c1a60ef 100644
--- a/drivers/staging/Makefile
+++ b/drivers/staging/Makefile
@@ -58,4 +58,3 @@ obj-$(CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI4) += ste_rmi4/
obj-$(CONFIG_DRM_PSB) += gma500/
obj-$(CONFIG_INTEL_MEI) += mei/
obj-$(CONFIG_MFD_NVEC) += nvec/
-obj-$(CONFIG_DVB_AS102) += media/as102/
--
1.7.6.4
prev parent reply other threads:[~2011-11-02 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1320233265.git.mchehab@redhat.com>
2011-11-02 11:45 ` [PATCH 2/3] staging: Move media drivers to staging/media Mauro Carvalho Chehab
2011-11-02 11:45 ` [PATCH 1/3] [media] move cx25821 out of staging Mauro Carvalho Chehab
2011-11-02 11:45 ` Mauro Carvalho Chehab [this message]
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=20111102094508.5a4eded5@redhat.com \
--to=mchehab@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-media@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 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.