Don't always show debug messages

CONFIG_EXFAT_DEBUG_MSG is always defined (either by Kconfig if on, or
exfat_config.h since 89d7aab6) so currently debugging messages are
always on.
Merge pull request #32 from ianw/debug

Don't always show debug messages
EXFAT: init sector value, and build in -O2
FIX Exfat function selection for Linux 3.13.1 main line.
Simplified the installation instructions
Merged 2 Makefiles into 1
Delete Makefile.module
Update README.md
exFAT (Samsung OSRC) bump to 1.2.5 + our stuff = 1.2.7

https://gerrit.omnirom.org/#/c/3937/
Fixed wrong PATH for ready module, when using standalone build.

Thanks to Chris Clayton <chris2553@googlemail.com>

he sent me this.

--- exfat/Makefile      2013-11-30 09:49:05.451945664 +0000
+++ exfat/Makefile.fixed        2014-01-05 09:13:22.643866902 +0000
@@ -17,6 +17,7 @@ EXTRA_FLAGS += -I$(PWD)

 #KDIR  := /usr/src/linux/
 KDIR   := /lib/modules/$(shell uname -r)/build
+MDIR   := /lib/modules/$(shell uname -r)
 PWD            := $(shell pwd)

 export CONFIG_EXFAT_FS := m
@@ -31,12 +32,12 @@ help:
        $(MAKE) -C $(KDIR) M=$(PWD) help

 install: exfat.ko
-       rm -f ${KDIR}/../kernel/fs/exfat/exfat.ko
-       install -m644 -b -D exfat.ko ${KDIR}/../kernel/fs/exfat/exfat.ko
+       rm -f ${MDIR}/kernel/fs/exfat/exfat.ko
+       install -m644 -b -D exfat.ko ${MDIR}/kernel/fs/exfat/exfat.ko
        depmod -aq

 uninstall:
-       rm -rf ${KDIR}/../kernel/fs/exfat
+       rm -rf ${MDIR}/kernel/fs/exfat
        depmod -aq

 endif

I find that the module is installed in the wrong place.
For example, if the exfat source is located in $HOME/kernel/exfat,
the module is installed as $HOME/kernel/kernel/fs/exfat/exfat.ko.
This is because KDIR refers to the module's source directory,
not the directory in which the kernel and its modules are installed.

The patch below fixes this.
new patch to Makefile for building as stand alone.

I've been thinking about the patch I submitted and have concluded that it could have been much better.

Now that the patch has been applied, if someone wants to build and install the exfat module for a kernel other than the one currently running,
(s)he has to provide values for both KDIR and MDIR when calling make.
Clearly that is not good.
That can, however, be trivially fixed by changing the assignment to MDIR as follows:

MDIR   := $(shell dirname ${KDIR})

In addition, however, in my experience of building external modules a user can set KDIR to any path to the kernel source.
For example, on my system the source for the currently-running kernel is in $HOME/kernel/linux-$(uname-r)
and it should be possible to use that as a value for KDIR instead of /lib/modules/$(uname -r)/build.
The patch below implements this idea as well as fixing the KDIR+MDIR badness I describe above.

Trivially, the patch also aligns the assignment to PWD with the earlier assignments.

Signed-off-by: Chris Clayton <chris2553@googlemail.com>
iov_iter_count is still not supported in main line.
EXFAT: merge Samsung Galaxy source update! and BUMP to 1.2.8
Since kernel version 3.10 d_hash and d_compare
do not need inode to be passed as a argument
Merge pull request #38 from torstehu/fix-dentry-operations

Since mainline v3.10 d_hash and d_compare
Update ReadMe. this driver was developed for ARM Android Kernel.

For other builds we need to rewrite, and no one will do that...
exfat_super.c: fix misplaced #ifdef CONFIG_EXFAT_KERNEL_DEBUG

Signed-off-by: Paul Reioux <reioux@gmail.com>
Merge pull request #40 from faux123/master

exfat_super.c: fix misplaced #ifdef CONFIG_EXFAT_KERNEL_DEBUG