All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Daniel Baluta <daniel.baluta@intel.com>
Cc: jic23@kernel.org, jlbec@evilplan.org, lars@metafoo.de,
	knaack.h@gmx.de, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, octavian.purdila@intel.com,
	pmeerw@pmeerw.net
Subject: Re: [PATCH v2 1/3] iio: configfs: Add configfs support to IIO
Date: Sat, 04 Apr 2015 20:26:05 +0200	[thread overview]
Message-ID: <1428171965.634.35.camel@x220> (raw)
In-Reply-To: <1428076680-28005-2-git-send-email-daniel.baluta@intel.com>

On Fri, 2015-04-03 at 18:57 +0300, Daniel Baluta wrote:
> --- a/drivers/iio/Kconfig
> +++ b/drivers/iio/Kconfig
> +config IIO_CONFIGFS
> +	tristate "Enable IIO configuration via configfs"
> +	select CONFIGFS_FS
> +	help
> +	  This allows configuring various IIO bits through configfs
> +	  (e.g. software triggers). For more info see
> +	  Documentation/iio/iio_configfs.txt.

> --- a/drivers/iio/Makefile
> +++ b/drivers/iio/Makefile
> @@ -5,6 +5,7 @@
>  obj-$(CONFIG_IIO) += industrialio.o
>  industrialio-y := industrialio-core.o industrialio-event.o inkern.o
>  industrialio-$(CONFIG_IIO_BUFFER) += industrialio-buffer.o
> +industrialio-$(CONFIG_IIO_CONFIGFS) += industrialio-configfs.o
>  industrialio-$(CONFIG_IIO_TRIGGER) += industrialio-trigger.o
>  industrialio-$(CONFIG_IIO_BUFFER_CB) += buffer_cb.o

It seems I didn't pay attention to this Makefile the first time I looked
at this series. And actually reading it I noticed that
industrialio-configfs.o can only be part of the industrial.ko module,
can't it? So this Makefile doesn't allow to build a separate
industrialio-configfs.ko module, right? If so, my previous review, in
which I claimed to spot a nit, was a waste of our time.

Because I now experienced that if this gets build with CONFIG_IIO=m and
CONFIG_IIO_CONFIGFS=y one gets: 
    $ make -C ../.. CONFIG_IIO_CONFIGFS=y M=$PWD industrialio.ko
    make: Entering directory `[...]'
      CC [M]  [...]/drivers/iio/industrialio-core.o
      CC [M]  [...]/linux/drivers/iio/industrialio-event.o
      CC [M]  [...]drivers/iio/inkern.o
      CC [M]  [...]/drivers/iio/industrialio-buffer.o
      CC [M]  [...]/drivers/iio/industrialio-configfs.o
      CC [M]  [...]/drivers/iio/industrialio-trigger.o
      CC [M]  [...]/drivers/iio/buffer_cb.o
      LD [M]  [...]/drivers/iio/industrialio.o
    [...]/drivers/iio/industrialio-configfs.o: In function `iio_configfs_init':
    industrialio-configfs.c:(.init.text+0x0): multiple definition of `init_module'
    [...]/drivers/iio/industrialio-core.o:industrialio-core.c:(.init.text+0x0): first defined here
    [...]/drivers/iio/industrialio-configfs.o: In function `iio_configfs_exit':
    industrialio-configfs.c:(.exit.text+0x0): multiple definition of `cleanup_module'
    [...]/drivers/iio/industrialio-core.o:industrialio-core.c:(.exit.text+0x0): first defined here
    make[1]: *** [[...]/drivers/iio/industrialio.o] Error 1
    make: *** [industrialio.ko] Error 2
    make: Leaving directory `[...]'

(I didn't yet test other configurations.)

So before I waste even more of your time: were you trying to make
configfs support a part of the industrialio module or were you trying to
make configfs support available as a separate module?

Thanks,


Paul Bolle

  reply	other threads:[~2015-04-04 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 15:57 [PATCH v2 0/3] Add initial configfs support for IIO Daniel Baluta
2015-04-03 15:57 ` [PATCH v2 1/3] iio: configfs: Add configfs support to IIO Daniel Baluta
2015-04-04 18:26   ` Paul Bolle [this message]
2015-04-06 13:42     ` Daniel Baluta
2015-04-03 15:57 ` [PATCH v2 2/3] iio: trigger: Add support for highres timer trigger type Daniel Baluta
2015-04-03 15:58 ` [PATCH v2 3/3] iio: Documentation: Add documentation for IIO configfs Daniel Baluta
2015-04-04 16:33   ` Paul Bolle

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=1428171965.634.35.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=jlbec@evilplan.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=octavian.purdila@intel.com \
    --cc=pmeerw@pmeerw.net \
    /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.