Re: [PATCH] samples: kdbus: build kdbus-workers conditionally

From: Andrew Morton
Date: Wed Apr 01 2015 - 17:41:27 EST


On Wed, 1 Apr 2015 14:47:20 +0200 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, Mar 31, 2015 at 03:11:34PM +0200, Daniel Mack wrote:
> > Give the kdbus sample its own config switch and only build it if it's
> > explicitly switched on.
> >
> > Signed-off-by: Daniel Mack <daniel@xxxxxxxxxx>
> > Reviewed-by: David Herrmann <dh.herrmann@xxxxxxxxx>
> > Reported-by: Jiri Slaby <jslaby@xxxxxxx>
> > ---
> > samples/Kconfig | 7 +++++++
> > samples/kdbus/Makefile | 2 +-
> > 2 files changed, 8 insertions(+), 1 deletion(-)
>
> Now applied, thanks.

Is this going to fix i386 allmodconfig, currently unhappy on my Fedora
Core 6 (lol) machine?

samples/kdbus/kdbus-workers.c:73:26: error: sys/signalfd.h: No such file or directory
samples/kdbus/kdbus-workers.c: In function 'master_new':
samples/kdbus/kdbus-workers.c:231: warning: implicit declaration of function 'signalfd'
samples/kdbus/kdbus-workers.c:231: error: 'SFD_CLOEXEC' undeclared (first use in this function)
samples/kdbus/kdbus-workers.c:231: error: (Each undeclared identifier is reported only once
samples/kdbus/kdbus-workers.c:231: error: for each function it appears in.)
samples/kdbus/kdbus-workers.c: In function 'master_handle_signal':
samples/kdbus/kdbus-workers.c:406: error: storage size of 'val' isn't known
samples/kdbus/kdbus-workers.c:406: warning: unused variable 'val'
samples/kdbus/kdbus-workers.c: In function 'child_run':
samples/kdbus/kdbus-workers.c:773: error: 'CLOCK_MONOTONIC_COARSE' undeclared (first use in this function)
samples/kdbus/kdbus-workers.c: In function 'bus_open_connection':
samples/kdbus/kdbus-workers.c:1038: error: 'O_CLOEXEC' undeclared (first use in this function)
samples/kdbus/kdbus-workers.c: In function 'bus_make':
samples/kdbus/kdbus-workers.c:1275: error: 'O_CLOEXEC' undeclared (first use in this function)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/