[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201103281659.45929.arnd@arndb.de>
Date: Mon, 28 Mar 2011 16:59:45 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Greg KH <gregkh@...e.de>
Cc: "Par-Gunnar HJALMDAHL" <par-gunnar.p.hjalmdahl@...ricsson.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
Linus Walleij <linus.walleij@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
Pavan Savoy <pavan_savoy@...y.com>,
Vitaly Wool <vitalywool@...il.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Marcel Holtmann <marcel@...tmann.org>,
Lukasz Rymanowski <Lukasz.Rymanowski@...to.com>,
Linus WALLEIJ <linus.walleij@...ricsson.com>,
"Par-Gunnar Hjalmdahl" <pghatwork@...il.com>,
Lee Jones <lee.jones@...aro.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>
Subject: Re: [PATCH v2 2/2] mach-ux500: Add CG2900 devices
On Monday 28 March 2011, Greg KH wrote:
> >
> > But how should I then do this? As I understood it I was told that I should
> > call an init function, but I was not allowed to add any staging folder
> > inclusion in the board config makefile. And now I can't do any extern
> > declaration either. I don't really see how I could do it then.
>
> Why can't you add a staging folder inclusion? You could do that, and
> properly set up your .h file so that if the driver is not built, your
> code still properly builds and runs.
That would work as well, along with the two solutions I suggested.
I believe Pär-Gunnar was trying to avoid #ifdefs, and the patch actually
contains alternative files implementing cg2900_init_board as a stub
when CONFIG_CG2900 is set, so the intent was clearly there:
@@ -0,0 +1,18 @@
+#
+# Makefile for ST-Ericsson CG2900 connectivity combo controller
+#
+
+ccflags-y := \
+ -Idrivers/staging/cg2900/include \
+ -Iarch/arm/mach-ux500
+
+ifeq ($(CONFIG_CG2900),n)
+obj-y += board-mop500-nocg2900.o
+export-objs := board-mop500-nocg2900.o
+else
+obj-$(CONFIG_CG2900) += board-mop500-cg2900.o devices-cg2900.o
+export-objs := board-mop500-cg2900.o
+endif
+
I don't think that this works though, because the directory
is ignored when CONFIG_CG2900 is not set, and if it did work,
it would cause an empty function to be included in every
single kernel, not even limited to the ARM architecture.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists