kernel/linux: fix using custom location

Currently, extract and patch are skipped as thus:
- using a custom directory of pre-installed headers
- a correctly named directory already exists

Otherwise, extract and patch are done.

The current second condition is wrong, because it allows the following
sequence to happen:
- a non-custom kernel is used
- a previous build only partially extracted the non-custom sources
- that p[revious build broke during extraction (eg. incomplete tarball...)
- a subsequent build will find a properly named directory, and will
thus skip extract and patch, which is wrong

Fix that by following the conditions in this table:

Type | Extract | Patch
----------------------+---------+-------
Pre-installed headers | N | N
custom directory | N | N
custom tarball | Y | N
mainstream tarball | Y | Y

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: David Holsgrove <david.holsgrove@xilinx.com>

 diff -durN duma_2_5_14.orig/Makefile duma_2_5_14/Makefile

 --- duma_2_5_14.orig/Makefile	2008-03-13 00:54:10.000000000 +0100

 +++ duma_2_5_14/Makefile	2008-06-17 10:28:45.000000000 +0200

 @@ -93,10 +93,6 @@

  # also define 'WIN32'

  # some defaults:

 -CC=gcc

 -CXX=g++

 -AR=ar

 -RANLIB=ranlib

  INSTALL=install

  RM=rm

  RMFORCE=rm -f

 @@ -317,7 +313,7 @@

  createconf$(EXEPOSTFIX): createconf.o

  	- $(RMFORCE) createconf$(EXEPOSTFIX)

 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)

  tstheap$(EXEPOSTFIX): libduma.a tstheap.o

  	- $(RMFORCE) tstheap$(EXEPOSTFIX)

 @@ -378,7 +374,7 @@

  # define rules how to build objects for createconf

  #

  createconf.o:

 -	$(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@

 +	$(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@

  #