I'm compiling linux for an ARM board. I need to make some customized changes into an existing driver code present in the kernel repository and reload the driver.

I was expecting to find a ".ko" file in the driver directory after doing the make, but no such file exists. Apparently uImage/device tree image compilation doesn't work that way. 

Do I need to write my own Makefile for standalone device driver compilation?

It may be a silly question, but sorry I'm pretty new to kernel/device drivers.

EDIT:
I followed the process outlined here: <http://odroid.com/dokuwiki/doku.php?id=en:c1_building_kernel>
After git checkout and installing the cross-compiler(arm-linux-gnueabihf-gcc 4.9.2), I issue the basic make comands

```
$ make odroidc_defconfig
$ make -j4
$ make -j4 modules
$ make uImage

```

All the steps are successful. The last few lines of log look like

```
KSYM    .tmp_kallsyms1.o
KSYM    .tmp_kallsyms2.o
LD      vmlinux
SORTEX  vmlinux
SYSMAP  System.map
OBJCOPY arch/arm/boot/ccImage
Kernel: arch/arm/boot/ccImage is ready
Image arch/arm/boot/ccImage.lzo is ready
UIMAGE  arch/arm/boot/uImage
Image Name:   Linux-3.10.72
Created:      Sat Mar 28 22:44:45 2015
Image Type:   ARM Linux Kernel Image (lzo compressed)
Data Size:    5459649 Bytes = 5331.69 kB = 5.21 MB
Load Address: 00208000
Entry Point:  00208000
Image arch/arm/boot/uImage is ready

```

EDIT 2: Path to the driver code
<https://github.com/hardkernel/linux/tree/odroidc-3.10.y/drivers/amlogic/efuse>