Merge branch 'for-linus' of git://git.infradead.org/users/eparis/notify
authorLinus Torvalds <torvalds@linux-foundation.org>
Sat, 30 Oct 2010 18:50:37 +0000 (11:50 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sat, 30 Oct 2010 18:50:37 +0000 (11:50 -0700)
* 'for-linus' of git://git.infradead.org/users/eparis/notify: (22 commits)
  Ensure FMODE_NONOTIFY is not set by userspace
  make fanotify_read() restartable across signals
  fsnotify: remove alignment padding from fsnotify_mark on 64 bit builds
  fs/notify/fanotify/fanotify_user.c: fix warnings
  fanotify: Fix FAN_CLOSE comments
  fanotify: do not recalculate the mask if the ignored mask changed
  fanotify: ignore events on directories unless specifically requested
  fsnotify: rename FS_IN_ISDIR to FS_ISDIR
  fanotify: do not send events for irregular files
  fanotify: limit number of listeners per user
  fanotify: allow userspace to override max marks
  fanotify: limit the number of marks in a single fanotify group
  fanotify: allow userspace to override max queue depth
  fsnotify: implement a default maximum queue depth
  fanotify: ignore fanotify ignore marks if open writers
  fanotify: allow userspace to flush all marks
  fsnotify: call fsnotify_parent in perm events
  fsnotify: correctly handle return codes from listeners
  fanotify: use __aligned_u64 in fanotify userspace metadata
  fanotify: implement fanotify listener ordering
  ...

1026 files changed:
Documentation/DocBook/kgdb.tmpl
Documentation/coccinelle.txt
Documentation/kbuild/kconfig-language.txt
Documentation/kbuild/makefiles.txt
Documentation/kbuild/modules.txt
Kbuild
Kconfig [new file with mode: 0644]
MAINTAINERS
Makefile
README
arch/Kconfig
arch/alpha/Kconfig
arch/arm/Kconfig
arch/arm/configs/mx51_defconfig
arch/arm/include/asm/hardware/cache-l2x0.h
arch/arm/include/asm/kgdb.h
arch/arm/include/asm/memblock.h
arch/arm/include/asm/outercache.h
arch/arm/kernel/kgdb.c
arch/arm/kernel/machine_kexec.c
arch/arm/kernel/vmlinux.lds.S
arch/arm/mach-imx/mach-mx27_3ds.c
arch/arm/mach-ixp2000/core.c
arch/arm/mach-msm/Kconfig
arch/arm/mach-msm/board-halibut.c
arch/arm/mach-msm/include/mach/debug-macro.S
arch/arm/mach-msm/iommu_dev.c
arch/arm/mach-msm/timer.c
arch/arm/mach-mx25/Kconfig
arch/arm/mach-mx25/mach-mx25_3ds.c
arch/arm/mach-mx3/Kconfig
arch/arm/mach-mx3/devices.c
arch/arm/mach-mx3/mach-mx31_3ds.c
arch/arm/mach-mx3/mach-mx35_3ds.c
arch/arm/mach-mx5/Kconfig
arch/arm/mach-mx5/Makefile
arch/arm/mach-mx5/board-mx51_babbage.c
arch/arm/mach-mx5/clock-mx51.c
arch/arm/mach-mx5/cpu_op-mx51.c [new file with mode: 0644]
arch/arm/mach-mx5/cpu_op-mx51.h [new file with mode: 0644]
arch/arm/mach-mx5/devices-imx51.h
arch/arm/mach-omap2/board-4430sdp.c
arch/arm/mach-omap2/board-omap4panda.c
arch/arm/mach-omap2/omap4-common.c
arch/arm/mach-s3c2410/h1940-bluetooth.c
arch/arm/mach-s3c2410/include/mach/gpio.h
arch/arm/mach-s3c2410/include/mach/h1940-latch.h
arch/arm/mach-s3c2410/include/mach/regs-s3c2443-clock.h
arch/arm/mach-s3c2410/include/mach/vmalloc.h
arch/arm/mach-s3c2410/mach-h1940.c
arch/arm/mach-s3c2412/s3c2412.c
arch/arm/mach-s3c2416/Kconfig
arch/arm/mach-s3c2416/Makefile
arch/arm/mach-s3c2416/irq.c
arch/arm/mach-s3c2416/pm.c [new file with mode: 0644]
arch/arm/mach-s3c2416/s3c2416.c
arch/arm/mach-s3c2440/Kconfig
arch/arm/mach-s3c2440/mach-rx1950.c
arch/arm/mach-s3c2440/s3c244x.c
arch/arm/mach-s3c2443/s3c2443.c
arch/arm/mach-s3c24a0/include/mach/vmalloc.h
arch/arm/mach-s3c64xx/Kconfig
arch/arm/mach-s3c64xx/Makefile
arch/arm/mach-s3c64xx/dev-audio.c
arch/arm/mach-s3c64xx/gpiolib.c
arch/arm/mach-s3c64xx/include/mach/vmalloc.h
arch/arm/mach-s3c64xx/mach-mini6410.c [new file with mode: 0644]
arch/arm/mach-s3c64xx/mach-real6410.c
arch/arm/mach-s3c64xx/setup-fb-24bpp.c
arch/arm/mach-s3c64xx/setup-ide.c
arch/arm/mach-s3c64xx/setup-keypad.c
arch/arm/mach-s3c64xx/setup-sdhci-gpio.c
arch/arm/mach-s5p6442/Kconfig
arch/arm/mach-s5p6442/clock.c
arch/arm/mach-s5p6442/dev-audio.c
arch/arm/mach-s5p6442/dev-spi.c
arch/arm/mach-s5p6442/dma.c
arch/arm/mach-s5p6442/include/mach/regs-clock.h
arch/arm/mach-s5p6442/include/mach/vmalloc.h
arch/arm/mach-s5p64x0/Kconfig
arch/arm/mach-s5p64x0/clock-s5p6440.c
arch/arm/mach-s5p64x0/clock-s5p6450.c
arch/arm/mach-s5p64x0/clock.c
arch/arm/mach-s5p64x0/dev-audio.c
arch/arm/mach-s5p64x0/dev-spi.c
arch/arm/mach-s5p64x0/dma.c
arch/arm/mach-s5p64x0/include/mach/regs-clock.h
arch/arm/mach-s5p64x0/include/mach/vmalloc.h
arch/arm/mach-s5p64x0/setup-i2c0.c
arch/arm/mach-s5p64x0/setup-i2c1.c
arch/arm/mach-s5pc100/Kconfig
arch/arm/mach-s5pc100/Makefile
arch/arm/mach-s5pc100/clock.c
arch/arm/mach-s5pc100/dev-audio.c
arch/arm/mach-s5pc100/dev-spi.c
arch/arm/mach-s5pc100/dma.c
arch/arm/mach-s5pc100/gpiolib.c
arch/arm/mach-s5pc100/include/mach/gpio.h
arch/arm/mach-s5pc100/include/mach/irqs.h
arch/arm/mach-s5pc100/include/mach/map.h
arch/arm/mach-s5pc100/include/mach/regs-gpio.h
arch/arm/mach-s5pc100/include/mach/vmalloc.h
arch/arm/mach-s5pc100/irq-gpio.c [deleted file]
arch/arm/mach-s5pc100/mach-smdkc100.c
arch/arm/mach-s5pc100/setup-fb-24bpp.c
arch/arm/mach-s5pc100/setup-i2c0.c
arch/arm/mach-s5pc100/setup-i2c1.c
arch/arm/mach-s5pc100/setup-ide.c
arch/arm/mach-s5pc100/setup-keypad.c
arch/arm/mach-s5pc100/setup-sdhci-gpio.c
arch/arm/mach-s5pv210/Kconfig
arch/arm/mach-s5pv210/Makefile
arch/arm/mach-s5pv210/clock.c
arch/arm/mach-s5pv210/cpu.c
arch/arm/mach-s5pv210/cpufreq.c [new file with mode: 0644]
arch/arm/mach-s5pv210/dev-audio.c
arch/arm/mach-s5pv210/dev-spi.c
arch/arm/mach-s5pv210/dma.c
arch/arm/mach-s5pv210/gpiolib.c
arch/arm/mach-s5pv210/include/mach/irqs.h
arch/arm/mach-s5pv210/include/mach/map.h
arch/arm/mach-s5pv210/include/mach/pm-core.h [new file with mode: 0644]
arch/arm/mach-s5pv210/include/mach/regs-clock.h
arch/arm/mach-s5pv210/include/mach/regs-gpio.h
arch/arm/mach-s5pv210/include/mach/regs-sys.h [new file with mode: 0644]
arch/arm/mach-s5pv210/include/mach/vmalloc.h
arch/arm/mach-s5pv210/mach-aquila.c
arch/arm/mach-s5pv210/mach-goni.c
arch/arm/mach-s5pv210/mach-smdkc110.c
arch/arm/mach-s5pv210/mach-smdkv210.c
arch/arm/mach-s5pv210/mach-torbreck.c [new file with mode: 0644]
arch/arm/mach-s5pv210/pm.c [new file with mode: 0644]
arch/arm/mach-s5pv210/setup-fb-24bpp.c
arch/arm/mach-s5pv210/setup-i2c0.c
arch/arm/mach-s5pv210/setup-i2c1.c
arch/arm/mach-s5pv210/setup-i2c2.c
arch/arm/mach-s5pv210/setup-ide.c
arch/arm/mach-s5pv210/setup-keypad.c
arch/arm/mach-s5pv210/setup-sdhci-gpio.c
arch/arm/mach-s5pv210/sleep.S [new file with mode: 0644]
arch/arm/mach-s5pv310/Kconfig
arch/arm/mach-s5pv310/Makefile
arch/arm/mach-s5pv310/clock.c
arch/arm/mach-s5pv310/cpu.c
arch/arm/mach-s5pv310/gpiolib.c [new file with mode: 0644]
arch/arm/mach-s5pv310/hotplug.c [new file with mode: 0644]
arch/arm/mach-s5pv310/include/mach/irqs.h
arch/arm/mach-s5pv310/include/mach/map.h
arch/arm/mach-s5pv310/include/mach/regs-clock.h
arch/arm/mach-s5pv310/include/mach/regs-gpio.h [new file with mode: 0644]
arch/arm/mach-s5pv310/include/mach/regs-srom.h [new file with mode: 0644]
arch/arm/mach-s5pv310/include/mach/vmalloc.h
arch/arm/mach-s5pv310/irq-combiner.c
arch/arm/mach-s5pv310/irq-eint.c [new file with mode: 0644]
arch/arm/mach-s5pv310/mach-smdkc210.c [new file with mode: 0644]
arch/arm/mach-s5pv310/mach-smdkv310.c
arch/arm/mach-s5pv310/mach-universal_c210.c
arch/arm/mach-s5pv310/setup-i2c0.c
arch/arm/mach-s5pv310/setup-i2c1.c
arch/arm/mach-s5pv310/setup-i2c2.c
arch/arm/mach-s5pv310/setup-i2c3.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-i2c4.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-i2c5.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-i2c6.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-i2c7.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-sdhci-gpio.c [new file with mode: 0644]
arch/arm/mach-s5pv310/setup-sdhci.c [new file with mode: 0644]
arch/arm/mach-sa1100/cpu-sa1100.c
arch/arm/mach-shmobile/board-ap4evb.c
arch/arm/mach-shmobile/clock-sh7367.c
arch/arm/mach-shmobile/clock-sh7372.c
arch/arm/mach-shmobile/clock-sh7377.c
arch/arm/mach-shmobile/include/mach/sh7372.h
arch/arm/mach-shmobile/intc-sh7372.c
arch/arm/mach-shmobile/pfc-sh7372.c
arch/arm/mach-shmobile/setup-sh7367.c
arch/arm/mach-shmobile/setup-sh7372.c
arch/arm/mach-shmobile/setup-sh7377.c
arch/arm/mach-u300/clock.c
arch/arm/mach-u300/core.c
arch/arm/mach-u300/include/mach/u300-regs.h
arch/arm/mach-ux500/cpu.c
arch/arm/mm/Kconfig
arch/arm/mm/cache-fa.S
arch/arm/mm/cache-l2x0.c
arch/arm/mm/cache-v3.S
arch/arm/mm/cache-v4.S
arch/arm/mm/cache-v4wb.S
arch/arm/mm/cache-v4wt.S
arch/arm/mm/fault-armv.c
arch/arm/mm/init.c
arch/arm/mm/mmu.c
arch/arm/mm/proc-arm1020.S
arch/arm/mm/proc-arm1020e.S
arch/arm/mm/proc-arm1022.S
arch/arm/mm/proc-arm1026.S
arch/arm/mm/proc-arm920.S
arch/arm/mm/proc-arm922.S
arch/arm/mm/proc-arm925.S
arch/arm/mm/proc-arm926.S
arch/arm/mm/proc-arm940.S
arch/arm/mm/proc-arm946.S
arch/arm/mm/proc-feroceon.S
arch/arm/mm/proc-xsc3.S
arch/arm/mm/proc-xscale.S
arch/arm/plat-mxc/Makefile
arch/arm/plat-mxc/cpufreq.c [new file with mode: 0644]
arch/arm/plat-mxc/devices/Kconfig
arch/arm/plat-mxc/devices/Makefile
arch/arm/plat-mxc/devices/platform-gpio_keys.c [new file with mode: 0644]
arch/arm/plat-mxc/gpio.c
arch/arm/plat-mxc/include/mach/devices-common.h
arch/arm/plat-mxc/include/mach/iomux-mx51.h
arch/arm/plat-mxc/include/mach/mx31.h
arch/arm/plat-mxc/include/mach/mx35.h
arch/arm/plat-mxc/include/mach/mxc.h
arch/arm/plat-pxa/include/plat/pxa3xx_nand.h
arch/arm/plat-s3c24xx/Kconfig
arch/arm/plat-s3c24xx/common-smdk.c
arch/arm/plat-s3c24xx/gpiolib.c
arch/arm/plat-s5p/Kconfig
arch/arm/plat-s5p/Makefile
arch/arm/plat-s5p/clock.c
arch/arm/plat-s5p/include/plat/irqs.h
arch/arm/plat-s5p/include/plat/map-s5p.h
arch/arm/plat-s5p/include/plat/s5p-clock.h
arch/arm/plat-s5p/irq-eint.c
arch/arm/plat-s5p/irq-gpioint.c [new file with mode: 0644]
arch/arm/plat-s5p/irq-pm.c [new file with mode: 0644]
arch/arm/plat-s5p/pm.c [new file with mode: 0644]
arch/arm/plat-samsung/Kconfig
arch/arm/plat-samsung/Makefile
arch/arm/plat-samsung/dev-hsmmc.c
arch/arm/plat-samsung/dev-hsmmc1.c
arch/arm/plat-samsung/dev-hsmmc2.c
arch/arm/plat-samsung/dev-hsmmc3.c
arch/arm/plat-samsung/dev-i2c2.c
arch/arm/plat-samsung/dev-i2c3.c [new file with mode: 0644]
arch/arm/plat-samsung/dev-i2c4.c [new file with mode: 0644]
arch/arm/plat-samsung/dev-i2c5.c [new file with mode: 0644]
arch/arm/plat-samsung/dev-i2c6.c [new file with mode: 0644]
arch/arm/plat-samsung/dev-i2c7.c [new file with mode: 0644]
arch/arm/plat-samsung/gpio-config.c
arch/arm/plat-samsung/gpio.c
arch/arm/plat-samsung/include/plat/audio.h
arch/arm/plat-samsung/include/plat/devs.h
arch/arm/plat-samsung/include/plat/gpio-cfg-helpers.h
arch/arm/plat-samsung/include/plat/gpio-cfg.h
arch/arm/plat-samsung/include/plat/gpio-core.h
arch/arm/plat-samsung/include/plat/iic.h
arch/arm/plat-samsung/include/plat/map-base.h
arch/arm/plat-samsung/include/plat/nand-core.h [new file with mode: 0644]
arch/arm/plat-samsung/include/plat/sdhci.h
arch/arm/plat-samsung/pm-gpio.c
arch/arm/plat-samsung/s3c-pl330.c
arch/avr32/Kconfig
arch/blackfin/Kconfig
arch/blackfin/kernel/kgdb.c
arch/cris/Kconfig
arch/frv/Kconfig
arch/h8300/Kconfig
arch/ia64/Kconfig
arch/ia64/kernel/perfmon.c
arch/m32r/Kconfig
arch/m68k/Kconfig
arch/m68knommu/Kconfig
arch/microblaze/Kconfig
arch/mips/Kconfig
arch/mips/Kconfig.debug
arch/mips/Makefile
arch/mips/ar7/gpio.c
arch/mips/ar7/platform.c
arch/mips/ar7/prom.c
arch/mips/ar7/setup.c
arch/mips/bcm63xx/cpu.c
arch/mips/cavium-octeon/Kconfig
arch/mips/cavium-octeon/csrc-octeon.c
arch/mips/cavium-octeon/dma-octeon.c
arch/mips/cavium-octeon/executive/cvmx-l2c.c
arch/mips/cavium-octeon/octeon-platform.c
arch/mips/cavium-octeon/serial.c
arch/mips/cavium-octeon/setup.c
arch/mips/include/asm/atomic.h
arch/mips/include/asm/bitops.h
arch/mips/include/asm/bootinfo.h
arch/mips/include/asm/cmpxchg.h
arch/mips/include/asm/cpu.h
arch/mips/include/asm/device.h
arch/mips/include/asm/dma-mapping.h
arch/mips/include/asm/dma.h
arch/mips/include/asm/local.h
arch/mips/include/asm/mach-ar7/ar7.h
arch/mips/include/asm/mach-ar7/gpio.h
arch/mips/include/asm/mach-bcm63xx/bcm963xx_tag.h [new file with mode: 0644]
arch/mips/include/asm/mach-cavium-octeon/cpu-feature-overrides.h
arch/mips/include/asm/mach-cavium-octeon/dma-coherence.h
arch/mips/include/asm/mach-ip27/dma-coherence.h
arch/mips/include/asm/mach-ip32/dma-coherence.h
arch/mips/include/asm/mach-jazz/dma-coherence.h
arch/mips/include/asm/mipsregs.h
arch/mips/include/asm/octeon/cvmx-agl-defs.h
arch/mips/include/asm/octeon/cvmx-asm.h
arch/mips/include/asm/octeon/cvmx-ciu-defs.h
arch/mips/include/asm/octeon/cvmx-gpio-defs.h
arch/mips/include/asm/octeon/cvmx-iob-defs.h
arch/mips/include/asm/octeon/cvmx-ipd-defs.h
arch/mips/include/asm/octeon/cvmx-l2c-defs.h
arch/mips/include/asm/octeon/cvmx-l2c.h
arch/mips/include/asm/octeon/cvmx-l2d-defs.h
arch/mips/include/asm/octeon/cvmx-l2t-defs.h
arch/mips/include/asm/octeon/cvmx-led-defs.h
arch/mips/include/asm/octeon/cvmx-mio-defs.h
arch/mips/include/asm/octeon/cvmx-mixx-defs.h
arch/mips/include/asm/octeon/cvmx-npei-defs.h
arch/mips/include/asm/octeon/cvmx-npi-defs.h
arch/mips/include/asm/octeon/cvmx-pci-defs.h
arch/mips/include/asm/octeon/cvmx-pciercx-defs.h
arch/mips/include/asm/octeon/cvmx-pescx-defs.h
arch/mips/include/asm/octeon/cvmx-pexp-defs.h
arch/mips/include/asm/octeon/cvmx-pow-defs.h
arch/mips/include/asm/octeon/cvmx-rnm-defs.h
arch/mips/include/asm/octeon/cvmx-smix-defs.h
arch/mips/include/asm/octeon/cvmx-uctlx-defs.h [new file with mode: 0644]
arch/mips/include/asm/octeon/octeon-model.h
arch/mips/include/asm/octeon/octeon.h
arch/mips/include/asm/octeon/pci-octeon.h
arch/mips/include/asm/perf_event.h [new file with mode: 0644]
arch/mips/include/asm/pgtable-64.h
arch/mips/include/asm/processor.h
arch/mips/include/asm/system.h
arch/mips/include/asm/thread_info.h
arch/mips/include/asm/uaccess.h
arch/mips/kernel/Makefile
arch/mips/kernel/cpu-probe.c
arch/mips/kernel/irq.c
arch/mips/kernel/perf_event.c [new file with mode: 0644]
arch/mips/kernel/perf_event_mipsxx.c [new file with mode: 0644]
arch/mips/kernel/setup.c
arch/mips/kernel/traps.c
arch/mips/kernel/unaligned.c
arch/mips/loongson/Kconfig
arch/mips/math-emu/cp1emu.c
arch/mips/mm/c-octeon.c
arch/mips/mm/c-r4k.c
arch/mips/mm/dma-default.c
arch/mips/mm/fault.c
arch/mips/mm/sc-mips.c
arch/mips/mm/tlbex.c
arch/mips/mm/uasm.c
arch/mips/pci/pci-octeon.c
arch/mips/pci/pcie-octeon.c
arch/mn10300/Kconfig
arch/parisc/Kconfig
arch/powerpc/Kconfig
arch/powerpc/include/asm/fsl_lbc.h
arch/powerpc/include/asm/kgdb.h
arch/powerpc/kernel/kgdb.c
arch/powerpc/platforms/cell/spufs/inode.c
arch/powerpc/sysdev/fsl_lbc.c
arch/s390/Kconfig
arch/s390/hypfs/hypfs_diag.c
arch/s390/hypfs/inode.c
arch/s390/include/asm/dasd.h
arch/s390/kernel/asm-offsets.c
arch/s390/kernel/early.c
arch/s390/kernel/entry.S
arch/s390/kernel/entry64.S
arch/s390/kernel/kprobes.c
arch/s390/kernel/setup.c
arch/s390/kernel/sysinfo.c
arch/s390/kernel/topology.c
arch/s390/kernel/vdso32/clock_getres.S
arch/s390/kernel/vdso32/clock_gettime.S
arch/s390/kernel/vdso64/clock_getres.S
arch/s390/kernel/vdso64/clock_gettime.S
arch/score/Kconfig
arch/sh/Kconfig
arch/sh/boards/mach-ap325rxa/setup.c
arch/sh/boards/mach-ecovec24/setup.c
arch/sh/boards/mach-kfr2r09/setup.c
arch/sh/boards/mach-migor/setup.c
arch/sh/boards/mach-se/7724/setup.c
arch/sparc/Kconfig
arch/sparc/include/asm/jump_label.h
arch/sparc/kernel/irq_32.c
arch/sparc/kernel/leon_smp.c
arch/sparc/kernel/rtrap_32.S
arch/sparc/kernel/rtrap_64.S
arch/sparc/mm/fault_32.c
arch/tile/Kconfig
arch/um/Kconfig.common
arch/x86/Kconfig
arch/x86/Makefile_32.cpu
arch/x86/include/asm/acpi.h
arch/x86/include/asm/io.h
arch/x86/include/asm/io_apic.h
arch/x86/include/asm/pci.h
arch/x86/include/asm/pci_x86.h
arch/x86/include/asm/uv/uv_hub.h
arch/x86/include/asm/x86_init.h
arch/x86/include/asm/xen/pci.h [new file with mode: 0644]
arch/x86/kernel/acpi/boot.c
arch/x86/kernel/alternative.c
arch/x86/kernel/apic/io_apic.c
arch/x86/kernel/apic/x2apic_uv_x.c
arch/x86/kernel/irq_32.c
arch/x86/kernel/kgdb.c
arch/x86/kernel/x86_init.c
arch/x86/mm/numa_64.c
arch/x86/pci/Makefile
arch/x86/pci/common.c
arch/x86/pci/i386.c
arch/x86/pci/xen.c [new file with mode: 0644]
arch/x86/xen/Kconfig
arch/x86/xen/enlighten.c
arch/x86/xen/mmu.c
arch/x86/xen/pci-swiotlb-xen.c
arch/x86/xen/setup.c
arch/x86/xen/smp.c
arch/xtensa/Kconfig
drivers/ata/pata_octeon_cf.c
drivers/base/devtmpfs.c
drivers/base/power/runtime.c
drivers/block/xen-blkfront.c
drivers/char/agp/parisc-agp.c
drivers/char/hvc_xen.c
drivers/char/tty_audit.c
drivers/dma/Kconfig
drivers/gpio/Kconfig
drivers/gpio/Makefile
drivers/gpio/stmpe-gpio.c
drivers/gpio/vx855_gpio.c [new file with mode: 0644]
drivers/gpio/wm8994-gpio.c
drivers/i2c/busses/Kconfig
drivers/i2c/busses/Makefile
drivers/i2c/busses/i2c-intel-mid.c [new file with mode: 0644]
drivers/i2c/busses/i2c-nomadik.c
drivers/i2c/busses/i2c-s3c2410.c
drivers/ide/hpt366.c
drivers/ide/ide-dma.c
drivers/infiniband/hw/ipath/ipath_fs.c
drivers/infiniband/hw/qib/qib_fs.c
drivers/input/misc/max8925_onkey.c
drivers/input/xen-kbdfront.c
drivers/isdn/capi/capifs.c
drivers/leds/leds-88pm860x.c
drivers/md/bitmap.c
drivers/md/bitmap.h
drivers/md/faulty.c
drivers/md/md.c
drivers/md/md.h
drivers/md/raid1.c
drivers/md/raid1.h
drivers/md/raid10.c
drivers/md/raid5.c
drivers/mfd/88pm860x-core.c
drivers/mfd/Kconfig
drivers/mfd/Makefile
drivers/mfd/ab3100-core.c
drivers/mfd/ab8500-core.c
drivers/mfd/ab8500-debugfs.c [new file with mode: 0644]
drivers/mfd/ab8500-i2c.c [new file with mode: 0644]
drivers/mfd/ab8500-spi.c
drivers/mfd/da903x.c
drivers/mfd/ezx-pcap.c
drivers/mfd/htc-pasic3.c
drivers/mfd/jz4740-adc.c
drivers/mfd/max8925-core.c
drivers/mfd/max8998-irq.c [new file with mode: 0644]
drivers/mfd/max8998.c
drivers/mfd/mc13783-core.c [deleted file]
drivers/mfd/mc13xxx-core.c [new file with mode: 0644]
drivers/mfd/mfd-core.c
drivers/mfd/pcf50633-core.c
drivers/mfd/sh_mobile_sdhi.c
drivers/mfd/stmpe.c
drivers/mfd/tc6393xb.c
drivers/mfd/timberdale.c
drivers/mfd/tps6507x.c
drivers/mfd/tps6586x.c
drivers/mfd/twl-core.c
drivers/mfd/twl-core.h [new file with mode: 0644]
drivers/mfd/twl4030-irq.c
drivers/mfd/twl4030-power.c
drivers/mfd/twl6030-irq.c
drivers/mfd/vx855.c [new file with mode: 0644]
drivers/mfd/wm831x-core.c
drivers/mfd/wm831x-i2c.c [new file with mode: 0644]
drivers/mfd/wm831x-spi.c [new file with mode: 0644]
drivers/misc/Kconfig
drivers/misc/Makefile
drivers/misc/ab8500-pwm.c [new file with mode: 0644]
drivers/misc/ibmasm/ibmasmfs.c
drivers/misc/kgdbts.c
drivers/mmc/host/omap_hsmmc.c
drivers/mmc/host/sh_mmcif.c
drivers/mmc/host/tmio_mmc.c
drivers/mtd/chips/cfi_cmdset_0001.c
drivers/mtd/chips/cfi_cmdset_0002.c
drivers/mtd/chips/cfi_probe.c
drivers/mtd/chips/cfi_util.c
drivers/mtd/devices/block2mtd.c
drivers/mtd/devices/m25p80.c
drivers/mtd/devices/phram.c
drivers/mtd/maps/Kconfig
drivers/mtd/maps/Makefile
drivers/mtd/maps/bcm963xx-flash.c [new file with mode: 0644]
drivers/mtd/maps/gpio-addr-flash.c
drivers/mtd/maps/pcmciamtd.c
drivers/mtd/maps/physmap_of.c
drivers/mtd/mtd_blkdevs.c
drivers/mtd/mtdchar.c
drivers/mtd/mtdpart.c
drivers/mtd/mtdsuper.c
drivers/mtd/nand/Kconfig
drivers/mtd/nand/Makefile
drivers/mtd/nand/bf5xx_nand.c
drivers/mtd/nand/davinci_nand.c
drivers/mtd/nand/denali.c
drivers/mtd/nand/fsl_elbc_nand.c
drivers/mtd/nand/fsl_upm.c
drivers/mtd/nand/fsmc_nand.c [new file with mode: 0644]
drivers/mtd/nand/mpc5121_nfc.c
drivers/mtd/nand/nand_base.c
drivers/mtd/nand/nand_bbt.c
drivers/mtd/nand/nand_ids.c
drivers/mtd/nand/nandsim.c
drivers/mtd/nand/ndfc.c
drivers/mtd/nand/omap2.c
drivers/mtd/nand/pxa3xx_nand.c
drivers/mtd/nand/r852.c
drivers/mtd/nand/r852.h
drivers/mtd/ofpart.c
drivers/mtd/onenand/Kconfig
drivers/mtd/onenand/onenand_base.c
drivers/mtd/onenand/samsung.c
drivers/mtd/sm_ftl.h
drivers/net/Kconfig
drivers/net/atarilance.c
drivers/net/cxgb3/cxgb3_main.c
drivers/net/cxgb3/sge.c
drivers/net/e1000e/82571.c
drivers/net/e1000e/e1000.h
drivers/net/e1000e/netdev.c
drivers/net/igb/igb_main.c
drivers/net/igbvf/netdev.c
drivers/net/ixgb/ixgb_main.c
drivers/net/ixgbe/ixgbe_dcb.c
drivers/net/ixgbe/ixgbe_dcb.h
drivers/net/ixgbe/ixgbe_dcb_82599.c
drivers/net/ixgbe/ixgbe_dcb_82599.h
drivers/net/ixgbe/ixgbe_main.c
drivers/net/lib8390.c
drivers/net/netxen/netxen_nic_ctx.c
drivers/net/netxen/netxen_nic_main.c
drivers/net/stmmac/stmmac_main.c
drivers/net/wireless/ath/ath5k/attach.c
drivers/net/wireless/ath/ath9k/ath9k.h
drivers/net/wireless/ath/ath9k/hif_usb.c
drivers/net/wireless/ath/ath9k/main.c
drivers/net/wireless/ath/ath9k/rc.c
drivers/net/wireless/ath/ath9k/recv.c
drivers/net/wireless/ath/ath9k/xmit.c
drivers/net/wireless/b43/sdio.c
drivers/net/wireless/libertas/if_sdio.c
drivers/net/xen-netfront.c
drivers/oprofile/buffer_sync.c
drivers/oprofile/cpu_buffer.c
drivers/oprofile/cpu_buffer.h
drivers/oprofile/oprofilefs.c
drivers/oprofile/timer_int.c
drivers/pci/Kconfig
drivers/pci/Makefile
drivers/pci/bus.c
drivers/pci/msi.c
drivers/pci/xen-pcifront.c [new file with mode: 0644]
drivers/power/Kconfig
drivers/regulator/Kconfig
drivers/regulator/Makefile
drivers/regulator/ab8500.c
drivers/regulator/core.c
drivers/regulator/dummy.h
drivers/regulator/lp3972.c [new file with mode: 0644]
drivers/regulator/max8952.c [new file with mode: 0644]
drivers/regulator/max8998.c
drivers/rtc/Kconfig
drivers/rtc/Makefile
drivers/rtc/rtc-ab8500.c
drivers/rtc/rtc-max8998.c [new file with mode: 0644]
drivers/rtc/rtc-mc13783.c [deleted file]
drivers/rtc/rtc-mc13xxx.c [new file with mode: 0644]
drivers/s390/block/dasd_eckd.c
drivers/s390/block/dasd_eckd.h
drivers/s390/char/tape_core.c
drivers/s390/char/tape_std.c
drivers/staging/Kconfig
drivers/staging/Makefile
drivers/staging/autofs/init.c
drivers/staging/dream/Kconfig [deleted file]
drivers/staging/dream/Makefile [deleted file]
drivers/staging/dream/TODO [deleted file]
drivers/staging/dream/camera/Kconfig [deleted file]
drivers/staging/dream/camera/Makefile [deleted file]
drivers/staging/dream/camera/msm_camera.c [deleted file]
drivers/staging/dream/camera/msm_io7x.c [deleted file]
drivers/staging/dream/camera/msm_io8x.c [deleted file]
drivers/staging/dream/camera/msm_v4l2.c [deleted file]
drivers/staging/dream/camera/msm_vfe7x.c [deleted file]
drivers/staging/dream/camera/msm_vfe7x.h [deleted file]
drivers/staging/dream/camera/msm_vfe8x.c [deleted file]
drivers/staging/dream/camera/msm_vfe8x.h [deleted file]
drivers/staging/dream/camera/msm_vfe8x_proc.c [deleted file]
drivers/staging/dream/camera/msm_vfe8x_proc.h [deleted file]
drivers/staging/dream/camera/mt9d112.c [deleted file]
drivers/staging/dream/camera/mt9d112.h [deleted file]
drivers/staging/dream/camera/mt9d112_reg.c [deleted file]
drivers/staging/dream/camera/mt9p012.h [deleted file]
drivers/staging/dream/camera/mt9p012_fox.c [deleted file]
drivers/staging/dream/camera/mt9p012_reg.c [deleted file]
drivers/staging/dream/camera/mt9t013.c [deleted file]
drivers/staging/dream/camera/mt9t013.h [deleted file]
drivers/staging/dream/camera/mt9t013_reg.c [deleted file]
drivers/staging/dream/camera/s5k3e2fx.c [deleted file]
drivers/staging/dream/camera/s5k3e2fx.h [deleted file]
drivers/staging/dream/generic_gpio.c [deleted file]
drivers/staging/dream/gpio_axis.c [deleted file]
drivers/staging/dream/gpio_event.c [deleted file]
drivers/staging/dream/gpio_input.c [deleted file]
drivers/staging/dream/gpio_matrix.c [deleted file]
drivers/staging/dream/gpio_output.c [deleted file]
drivers/staging/dream/include/linux/android_pmem.h [deleted file]
drivers/staging/dream/include/linux/gpio_event.h [deleted file]
drivers/staging/dream/include/linux/msm_adsp.h [deleted file]
drivers/staging/dream/include/linux/msm_audio.h [deleted file]
drivers/staging/dream/include/linux/msm_rpcrouter.h [deleted file]
drivers/staging/dream/include/linux/wakelock.h [deleted file]
drivers/staging/dream/include/mach/camera.h [deleted file]
drivers/staging/dream/include/mach/msm_adsp.h [deleted file]
drivers/staging/dream/include/mach/msm_rpcrouter.h [deleted file]
drivers/staging/dream/include/mach/msm_smd.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audplaycmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audplaymsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audppcmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audppmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audpreproccmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audpreprocmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audreccmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5audrecmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5jpegcmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5jpegmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5lpmcmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5lpmmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5vdeccmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5vdecmsg.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5venccmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5vfecmdi.h [deleted file]
drivers/staging/dream/include/mach/qdsp5/qdsp5vfemsg.h [deleted file]
drivers/staging/dream/include/media/msm_camera.h [deleted file]
drivers/staging/dream/pmem.c [deleted file]
drivers/staging/dream/qdsp5/Makefile [deleted file]
drivers/staging/dream/qdsp5/adsp.c [deleted file]
drivers/staging/dream/qdsp5/adsp.h [deleted file]
drivers/staging/dream/qdsp5/adsp_6210.c [deleted file]
drivers/staging/dream/qdsp5/adsp_6220.c [deleted file]
drivers/staging/dream/qdsp5/adsp_6225.c [deleted file]
drivers/staging/dream/qdsp5/adsp_driver.c [deleted file]
drivers/staging/dream/qdsp5/adsp_info.c [deleted file]
drivers/staging/dream/qdsp5/adsp_jpeg_patch_event.c [deleted file]
drivers/staging/dream/qdsp5/adsp_jpeg_verify_cmd.c [deleted file]
drivers/staging/dream/qdsp5/adsp_lpm_verify_cmd.c [deleted file]
drivers/staging/dream/qdsp5/adsp_vfe_patch_event.c [deleted file]
drivers/staging/dream/qdsp5/adsp_vfe_verify_cmd.c [deleted file]
drivers/staging/dream/qdsp5/adsp_video_verify_cmd.c [deleted file]
drivers/staging/dream/qdsp5/adsp_videoenc_verify_cmd.c [deleted file]
drivers/staging/dream/qdsp5/audio_aac.c [deleted file]
drivers/staging/dream/qdsp5/audio_amrnb.c [deleted file]
drivers/staging/dream/qdsp5/audio_evrc.c [deleted file]
drivers/staging/dream/qdsp5/audio_in.c [deleted file]
drivers/staging/dream/qdsp5/audio_mp3.c [deleted file]
drivers/staging/dream/qdsp5/audio_out.c [deleted file]
drivers/staging/dream/qdsp5/audio_qcelp.c [deleted file]
drivers/staging/dream/qdsp5/audmgr.c [deleted file]
drivers/staging/dream/qdsp5/audmgr.h [deleted file]
drivers/staging/dream/qdsp5/audmgr_new.h [deleted file]
drivers/staging/dream/qdsp5/audpp.c [deleted file]
drivers/staging/dream/qdsp5/evlog.h [deleted file]
drivers/staging/dream/qdsp5/snd.c [deleted file]
drivers/staging/dream/synaptics_i2c_rmi.c [deleted file]
drivers/staging/dream/synaptics_i2c_rmi.h [deleted file]
drivers/staging/pohmelfs/inode.c
drivers/staging/smbfs/inode.c
drivers/usb/core/inode.c
drivers/usb/gadget/f_fs.c
drivers/usb/gadget/inode.c
drivers/usb/gadget/u_ether.c
drivers/usb/host/Kconfig
drivers/usb/host/Makefile
drivers/usb/host/ehci-hcd.c
drivers/usb/host/ehci-octeon.c [new file with mode: 0644]
drivers/usb/host/octeon2-common.c [new file with mode: 0644]
drivers/usb/host/ohci-hcd.c
drivers/usb/host/ohci-octeon.c [new file with mode: 0644]
drivers/usb/otg/twl4030-usb.c
drivers/video/msm/mddi.c
drivers/video/msm/mdp.c
drivers/video/sh_mipi_dsi.c
drivers/video/sh_mobile_hdmi.c
drivers/video/sh_mobile_lcdcfb.c
drivers/video/sh_mobile_lcdcfb.h [new file with mode: 0644]
drivers/video/xen-fbfront.c
drivers/watchdog/Kconfig
drivers/watchdog/Makefile
drivers/watchdog/bcm63xx_wdt.c [new file with mode: 0644]
drivers/watchdog/f71808e_wdt.c
drivers/watchdog/iTCO_wdt.c
drivers/watchdog/it8712f_wdt.c
drivers/watchdog/it87_wdt.c
drivers/watchdog/machzwd.c
drivers/watchdog/octeon-wdt-main.c
drivers/xen/Kconfig
drivers/xen/Makefile
drivers/xen/biomerge.c [new file with mode: 0644]
drivers/xen/events.c
drivers/xen/pci.c [new file with mode: 0644]
drivers/xen/xenbus/xenbus_client.c
drivers/xen/xenbus/xenbus_probe.c
drivers/xen/xenfs/super.c
fs/9p/vfs_super.c
fs/adfs/super.c
fs/affs/super.c
fs/afs/super.c
fs/anon_inodes.c
fs/autofs4/init.c
fs/befs/linuxvfs.c
fs/bfs/inode.c
fs/binfmt_misc.c
fs/block_dev.c
fs/btrfs/compression.c
fs/btrfs/ctree.c
fs/btrfs/ctree.h
fs/btrfs/dir-item.c
fs/btrfs/disk-io.c
fs/btrfs/extent-tree.c
fs/btrfs/extent_io.c
fs/btrfs/extent_io.h
fs/btrfs/extent_map.c
fs/btrfs/free-space-cache.c
fs/btrfs/free-space-cache.h
fs/btrfs/inode.c
fs/btrfs/ioctl.c
fs/btrfs/ioctl.h
fs/btrfs/ordered-data.c
fs/btrfs/relocation.c
fs/btrfs/root-tree.c
fs/btrfs/super.c
fs/btrfs/transaction.c
fs/btrfs/transaction.h
fs/btrfs/tree-defrag.c
fs/btrfs/tree-log.c
fs/btrfs/volumes.c
fs/btrfs/xattr.c
fs/btrfs/zlib.c
fs/ceph/super.c
fs/cifs/Kconfig
fs/cifs/cifsencrypt.c
fs/cifs/cifsfs.c
fs/cifs/cifsfs.h
fs/cifs/cifsglob.h
fs/cifs/cifspdu.h
fs/cifs/cifsproto.h
fs/cifs/cifssmb.c
fs/cifs/connect.c
fs/cifs/file.c
fs/cifs/inode.c
fs/cifs/misc.c
fs/cifs/sess.c
fs/cifs/transport.c
fs/coda/inode.c
fs/compat.c
fs/configfs/mount.c
fs/cramfs/inode.c
fs/debugfs/inode.c
fs/devpts/inode.c
fs/ecryptfs/ecryptfs_kernel.h
fs/ecryptfs/inode.c
fs/ecryptfs/keystore.c
fs/ecryptfs/main.c
fs/ecryptfs/super.c
fs/efs/super.c
fs/exofs/super.c
fs/ext2/super.c
fs/ext3/super.c
fs/ext4/inode.c
fs/ext4/super.c
fs/fat/namei_msdos.c
fs/fat/namei_vfat.c
fs/freevxfs/vxfs_super.c
fs/fs-writeback.c
fs/fuse/control.c
fs/fuse/inode.c
fs/gfs2/ops_fstype.c
fs/hfs/super.c
fs/hfsplus/super.c
fs/hostfs/hostfs_kern.c
fs/hpfs/super.c
fs/hppfs/hppfs.c
fs/hugetlbfs/inode.c
fs/internal.h
fs/isofs/inode.c
fs/jffs2/build.c
fs/jffs2/compr.c
fs/jffs2/compr.h
fs/jffs2/compr_lzo.c
fs/jffs2/compr_rtime.c
fs/jffs2/compr_rubin.c
fs/jffs2/compr_zlib.c
fs/jffs2/dir.c
fs/jffs2/erase.c
fs/jffs2/fs.c
fs/jffs2/gc.c
fs/jffs2/jffs2_fs_sb.h
fs/jffs2/nodelist.c
fs/jffs2/nodelist.h
fs/jffs2/scan.c
fs/jffs2/super.c
fs/jfs/super.c
fs/libfs.c
fs/logfs/dev_bdev.c
fs/logfs/dev_mtd.c
fs/logfs/logfs.h
fs/logfs/super.c
fs/minix/inode.c
fs/namei.c
fs/ncpfs/inode.c
fs/nfs/direct.c
fs/nfs/idmap.c
fs/nfs/nfs4proc.c
fs/nfs/pagelist.c
fs/nfs/super.c
fs/nfs/unlink.c
fs/nfsd/nfsctl.c
fs/nilfs2/super.c
fs/ntfs/super.c
fs/ocfs2/dlmfs/dlmfs.c
fs/ocfs2/super.c
fs/omfs/inode.c
fs/open.c
fs/openpromfs/inode.c
fs/pipe.c
fs/proc/root.c
fs/qnx4/inode.c
fs/ramfs/inode.c
fs/read_write.c
fs/reiserfs/super.c
fs/romfs/super.c
fs/squashfs/super.c
fs/squashfs/xattr.c
fs/squashfs/xattr.h
fs/squashfs/xattr_id.c
fs/super.c
fs/sysfs/mount.c
fs/sysv/super.c
fs/ubifs/super.c
fs/udf/super.c
fs/ufs/super.c
fs/xfs/linux-2.6/xfs_super.c
include/asm-generic/audit_change_attr.h
include/asm-generic/vmlinux.lds.h
include/linux/audit.h
include/linux/dccp.h
include/linux/fs.h
include/linux/i2c/twl.h
include/linux/jump_label.h
include/linux/kgdb.h
include/linux/mfd/88pm860x.h
include/linux/mfd/ab8500.h
include/linux/mfd/abx500.h
include/linux/mfd/core.h
include/linux/mfd/max8998-private.h
include/linux/mfd/max8998.h
include/linux/mfd/mc13783.h
include/linux/mfd/mc13xxx.h [new file with mode: 0644]
include/linux/mfd/pcf50633/core.h
include/linux/mfd/sh_mobile_sdhi.h
include/linux/mfd/stmpe.h
include/linux/mfd/tmio.h
include/linux/mfd/tps6586x.h
include/linux/mfd/wm831x/core.h
include/linux/mmc/sh_mmcif.h
include/linux/mtd/bbm.h
include/linux/mtd/cfi.h
include/linux/mtd/fsmc.h [new file with mode: 0644]
include/linux/mtd/inftl.h
include/linux/mtd/mtd.h
include/linux/mtd/nand.h
include/linux/mtd/partitions.h
include/linux/mtd/super.h
include/linux/ramfs.h
include/linux/regulator/lp3972.h [new file with mode: 0644]
include/linux/regulator/machine.h
include/linux/regulator/max8952.h [new file with mode: 0644]
include/linux/sched.h
include/linux/socket.h
include/linux/tty.h
include/linux/writeback.h
include/mtd/mtd-abi.h
include/mtd/mtd-user.h
include/net/ip_fib.h
include/video/sh_mobile_lcdc.h
include/xen/events.h
include/xen/interface/features.h
include/xen/interface/io/pciif.h [new file with mode: 0644]
include/xen/interface/io/xenbus.h
include/xen/interface/physdev.h
init/initramfs.c
ipc/mqueue.c
ipc/shm.c
kernel/audit.c
kernel/audit.h
kernel/audit_tree.c
kernel/audit_watch.c
kernel/auditfilter.c
kernel/auditsc.c
kernel/cgroup.c
kernel/cpuset.c
kernel/debug/debug_core.c
kernel/debug/kdb/kdb_main.c
kernel/jump_label.c
kernel/kprobes.c
kernel/sched.c
kernel/sched_fair.c
kernel/sched_stats.h
mm/mmap.c
mm/nommu.c
mm/shmem.c
net/compat.c
net/core/iovec.c
net/core/pktgen.c
net/dccp/ccid.h
net/dccp/ccids/ccid2.c
net/dccp/ccids/ccid2.h
net/dccp/ccids/ccid3.c
net/dccp/dccp.h
net/dccp/output.c
net/dccp/proto.c
net/dccp/timer.c
net/ipv4/fib_frontend.c
net/ipv4/fib_hash.c
net/ipv4/fib_trie.c
net/mac80211/debugfs_key.c
net/mac80211/main.c
net/netfilter/xt_socket.c
net/socket.c
net/sunrpc/rpc_pipe.c
samples/Kconfig
samples/Makefile
samples/kdb/Makefile [new file with mode: 0644]
samples/kdb/kdb_hello.c [new file with mode: 0644]
scripts/Makefile.clean
scripts/Makefile.lib
scripts/basic/docproc.c
scripts/coccicheck
scripts/coccinelle/api/alloc/drop_kmalloc_cast.cocci [moved from scripts/coccinelle/alloc/drop_kmalloc_cast.cocci with 100% similarity]
scripts/coccinelle/api/alloc/kzalloc-simple.cocci [moved from scripts/coccinelle/alloc/kzalloc-simple.cocci with 87% similarity]
scripts/coccinelle/api/err_cast.cocci [moved from scripts/coccinelle/err_cast.cocci with 100% similarity]
scripts/coccinelle/api/kstrdup.cocci [new file with mode: 0644]
scripts/coccinelle/api/memdup.cocci [new file with mode: 0644]
scripts/coccinelle/api/memdup_user.cocci [new file with mode: 0644]
scripts/coccinelle/api/resource_size.cocci [moved from scripts/coccinelle/resource_size.cocci with 100% similarity]
scripts/coccinelle/free/kfree.cocci [new file with mode: 0644]
scripts/coccinelle/iterators/fen.cocci [new file with mode: 0644]
scripts/coccinelle/iterators/itnull.cocci [new file with mode: 0644]
scripts/coccinelle/iterators/list_entry_update.cocci [new file with mode: 0644]
scripts/coccinelle/locks/call_kern.cocci [new file with mode: 0644]
scripts/coccinelle/locks/double_lock.cocci [new file with mode: 0644]
scripts/coccinelle/locks/flags.cocci [new file with mode: 0644]
scripts/coccinelle/locks/mini_lock.cocci [new file with mode: 0644]
scripts/coccinelle/misc/doubleinit.cocci [new file with mode: 0644]
scripts/coccinelle/misc/ifcol.cocci [new file with mode: 0644]
scripts/coccinelle/null/deref_null.cocci [moved from scripts/coccinelle/deref_null.cocci with 100% similarity]
scripts/coccinelle/null/eno.cocci [new file with mode: 0644]
scripts/coccinelle/null/kmerr.cocci [new file with mode: 0644]
scripts/coccinelle/tests/doublebitand.cocci [new file with mode: 0644]
scripts/coccinelle/tests/doubletest.cocci [new file with mode: 0644]
scripts/extract-ikconfig
scripts/kallsyms.c
scripts/kconfig/Makefile
scripts/kconfig/conf.c
scripts/kconfig/confdata.c
scripts/kconfig/expr.h
scripts/kconfig/gconf.c
scripts/kconfig/gconf.glade
scripts/kconfig/kxgettext.c
scripts/kconfig/lex.zconf.c_shipped
scripts/kconfig/lkc.h
scripts/kconfig/lkc_proto.h
scripts/kconfig/lxdialog/check-lxdialog.sh
scripts/kconfig/mconf.c
scripts/kconfig/menu.c
scripts/kconfig/nconf.c
scripts/kconfig/nconf.gui.c
scripts/kconfig/nconf.h
scripts/kconfig/qconf.cc
scripts/kconfig/qconf.h
scripts/kconfig/streamline_config.pl
scripts/kconfig/symbol.c
scripts/kconfig/util.c
scripts/kconfig/zconf.l
scripts/kconfig/zconf.tab.c_shipped
scripts/kconfig/zconf.y
scripts/mod/modpost.c
scripts/namespace.pl
scripts/package/builddeb
scripts/package/mkspec
scripts/recordmcount.c
scripts/recordmcount.h
scripts/setlocalversion
security/inode.c
security/selinux/selinuxfs.c
security/smack/smackfs.c
usr/Makefile
usr/initramfs_data.S
usr/initramfs_data.bz2.S [deleted file]
usr/initramfs_data.gz.S [deleted file]
usr/initramfs_data.lzma.S [deleted file]
usr/initramfs_data.lzo.S [deleted file]

index 490d862..d71b57f 100644 (file)
@@ -710,7 +710,18 @@ Task Addr       Pid   Parent [*] cpu State Thread     Command
         <listitem><para>A simple shell</para></listitem>
         <listitem><para>The kdb core command set</para></listitem>
         <listitem><para>A registration API to register additional kdb shell commands.</para>
-        <para>A good example of a self-contained kdb module is the "ftdump" command for dumping the ftrace buffer.  See: kernel/trace/trace_kdb.c</para></listitem>
+       <itemizedlist>
+        <listitem><para>A good example of a self-contained kdb module
+        is the "ftdump" command for dumping the ftrace buffer.  See:
+        kernel/trace/trace_kdb.c</para></listitem>
+        <listitem><para>For an example of how to dynamically register
+        a new kdb command you can build the kdb_hello.ko kernel module
+        from samples/kdb/kdb_hello.c.  To build this example you can
+        set CONFIG_SAMPLES=y and CONFIG_SAMPLE_KDB=m in your kernel
+        config.  Later run "modprobe kdb_hello" and the next time you
+        enter the kdb shell, you can run the "hello"
+        command.</para></listitem>
+       </itemizedlist></listitem>
         <listitem><para>The implementation for kdb_printf() which
         emits messages directly to I/O drivers, bypassing the kernel
         log.</para></listitem>
index cd2b028..4a276ea 100644 (file)
@@ -24,6 +24,9 @@ of many distributions, e.g. :
 You can get the latest version released from the Coccinelle homepage at
 http://coccinelle.lip6.fr/
 
+Information and tips about Coccinelle are also provided on the wiki
+pages at http://cocci.ekstranet.diku.dk/wiki/doku.php
+
 Once you have it, run the following command:
 
        ./configure
@@ -41,20 +44,22 @@ A Coccinelle-specific target is defined in the top level
 Makefile. This target is named 'coccicheck' and calls the 'coccicheck'
 front-end in the 'scripts' directory.
 
-Four modes are defined: report, patch, context, and org. The mode to
+Four modes are defined: patch, report, context, and org. The mode to
 use is specified by setting the MODE variable with 'MODE=<mode>'.
 
+'patch' proposes a fix, when possible.
+
 'report' generates a list in the following format:
   file:line:column-column: message
 
-'patch' proposes a fix, when possible.
-
 'context' highlights lines of interest and their context in a
 diff-like style.Lines of interest are indicated with '-'.
 
 'org' generates a report in the Org mode format of Emacs.
 
-Note that not all semantic patches implement all modes.
+Note that not all semantic patches implement all modes. For easy use
+of Coccinelle, the default mode is "chain" which tries the previous
+modes in the order above until one succeeds.
 
 To make a report for every semantic patch, run the following command:
 
@@ -68,9 +73,9 @@ To produce patches, run:
 
 
 The coccicheck target applies every semantic patch available in the
-subdirectories of 'scripts/coccinelle' to the entire Linux kernel.
+sub-directories of 'scripts/coccinelle' to the entire Linux kernel.
 
-For each semantic patch, a changelog message is proposed.  It gives a
+For each semantic patch, a commit message is proposed.  It gives a
 description of the problem being checked by the semantic patch, and
 includes a reference to Coccinelle.
 
@@ -93,12 +98,35 @@ or
        make coccicheck COCCI=<my_SP.cocci> MODE=report
 
 
+ Using Coccinelle on (modified) files
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To apply Coccinelle on a file basis, instead of a directory basis, the
+following command may be used:
+
+    make C=1 CHECK="scripts/coccicheck"
+
+To check only newly edited code, use the value 2 for the C flag, i.e.
+
+    make C=2 CHECK="scripts/coccicheck"
+
+This runs every semantic patch in scripts/coccinelle by default. The
+COCCI variable may additionally be used to only apply a single
+semantic patch as shown in the previous section.
+
+The "chain" mode is the default. You can select another one with the
+MODE variable explained above.
+
+In this mode, there is no information about semantic patches
+displayed, and no commit message proposed.
+
+
  Proposing new semantic patches
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 New semantic patches can be proposed and submitted by kernel
 developers. For sake of clarity, they should be organized in the
-subdirectories of 'scripts/coccinelle/'.
+sub-directories of 'scripts/coccinelle/'.
 
 
  Detailed description of the 'report' mode
@@ -111,7 +139,7 @@ Example:
 
 Running
 
-       make coccicheck MODE=report COCCI=scripts/coccinelle/err_cast.cocci
+       make coccicheck MODE=report COCCI=scripts/coccinelle/api/err_cast.cocci
 
 will execute the following part of the SmPL script.
 
@@ -149,7 +177,7 @@ identified.
 Example:
 
 Running
-       make coccicheck MODE=patch COCCI=scripts/coccinelle/err_cast.cocci
+       make coccicheck MODE=patch COCCI=scripts/coccinelle/api/err_cast.cocci
 
 will execute the following part of the SmPL script.
 
@@ -193,7 +221,7 @@ NOTE: The diff-like output generated is NOT an applicable patch. The
 Example:
 
 Running
-       make coccicheck MODE=context COCCI=scripts/coccinelle/err_cast.cocci
+       make coccicheck MODE=context COCCI=scripts/coccinelle/api/err_cast.cocci
 
 will execute the following part of the SmPL script.
 
@@ -228,7 +256,7 @@ diff -u -p /home/user/linux/crypto/ctr.c /tmp/nothing
 Example:
 
 Running
-       make coccicheck MODE=org COCCI=scripts/coccinelle/err_cast.cocci
+       make coccicheck MODE=org COCCI=scripts/coccinelle/api/err_cast.cocci
 
 will execute the following part of the SmPL script.
 
index b472e4e..2fe93ca 100644 (file)
@@ -322,7 +322,8 @@ mainmenu:
        "mainmenu" <prompt>
 
 This sets the config program's title bar if the config program chooses
-to use it.
+to use it. It should be placed at the top of the configuration, before any
+other statement.
 
 
 Kconfig hints
index c787ae5..0ef00bd 100644 (file)
@@ -776,6 +776,13 @@ This will delete the directory debian, including all subdirectories.
 Kbuild will assume the directories to be in the same relative path as the
 Makefile if no absolute path is specified (path does not start with '/').
 
+To exclude certain files from make clean, use the $(no-clean-files) variable.
+This is only a special case used in the top level Kbuild file:
+
+       Example:
+               #Kbuild
+               no-clean-files := $(bounds-file) $(offsets-file)
+
 Usually kbuild descends down in subdirectories due to "obj-* := dir/",
 but in the architecture makefiles where the kbuild infrastructure
 is not sufficient this sometimes needs to be explicit.
index 0767cf6..3fb39e0 100644 (file)
+Building External Modules
 
-In this document you will find information about:
-- how to build external modules
-- how to make your module use the kbuild infrastructure
-- how kbuild will install a kernel
-- how to install modules in a non-standard location
+This document describes how to build an out-of-tree kernel module.
 
 === Table of Contents
 
        === 1 Introduction
-       === 2 How to build external modules
-          --- 2.1 Building external modules
-          --- 2.2 Available targets
-          --- 2.3 Available options
-          --- 2.4 Preparing the kernel tree for module build
-          --- 2.5 Building separate files for a module
-       === 3. Example commands
-       === 4. Creating a kbuild file for an external module
-       === 5. Include files
-          --- 5.1 How to include files from the kernel include dir
-          --- 5.2 External modules using an include/ dir
-          --- 5.3 External modules using several directories
-       === 6. Module installation
-          --- 6.1 INSTALL_MOD_PATH
-          --- 6.2 INSTALL_MOD_DIR
-       === 7. Module versioning & Module.symvers
-          --- 7.1 Symbols from the kernel (vmlinux + modules)
-          --- 7.2 Symbols and external modules
-          --- 7.3 Symbols from another external module
-       === 8. Tips & Tricks
-          --- 8.1 Testing for CONFIG_FOO_BAR
+       === 2 How to Build External Modules
+          --- 2.1 Command Syntax
+          --- 2.2 Options
+          --- 2.3 Targets
+          --- 2.4 Building Separate Files
+       === 3. Creating a Kbuild File for an External Module
+          --- 3.1 Shared Makefile
+          --- 3.2 Separate Kbuild file and Makefile
+          --- 3.3 Binary Blobs
+          --- 3.4 Building Multiple Modules
+       === 4. Include Files
+          --- 4.1 Kernel Includes
+          --- 4.2 Single Subdirectory
+          --- 4.3 Several Subdirectories
+       === 5. Module Installation
+          --- 5.1 INSTALL_MOD_PATH
+          --- 5.2 INSTALL_MOD_DIR
+       === 6. Module Versioning
+          --- 6.1 Symbols From the Kernel (vmlinux + modules)
+          --- 6.2 Symbols and External Modules
+          --- 6.3 Symbols From Another External Module
+       === 7. Tips & Tricks
+          --- 7.1 Testing for CONFIG_FOO_BAR
 
 
 
 === 1. Introduction
 
-kbuild includes functionality for building modules both
-within the kernel source tree and outside the kernel source tree.
-The latter is usually referred to as external or "out-of-tree"
-modules and is used both during development and for modules that
-are not planned to be included in the kernel tree.
+"kbuild" is the build system used by the Linux kernel. Modules must use
+kbuild to stay compatible with changes in the build infrastructure and
+to pick up the right flags to "gcc." Functionality for building modules
+both in-tree and out-of-tree is provided. The method for building
+either is similar, and all modules are initially developed and built
+out-of-tree.
 
-What is covered within this file is mainly information to authors
-of modules. The author of an external module should supply
-a makefile that hides most of the complexity, so one only has to type
-'make' to build the module. A complete example will be presented in
-chapter 4, "Creating a kbuild file for an external module".
+Covered in this document is information aimed at developers interested
+in building out-of-tree (or "external") modules. The author of an
+external module should supply a makefile that hides most of the
+complexity, so one only has to type "make" to build the module. This is
+easily accomplished, and a complete example will be presented in
+section 3.
 
 
-=== 2. How to build external modules
+=== 2. How to Build External Modules
 
-kbuild offers functionality to build external modules, with the
-prerequisite that there is a pre-built kernel available with full source.
-A subset of the targets available when building the kernel is available
-when building an external module.
+To build external modules, you must have a prebuilt kernel available
+that contains the configuration and header files used in the build.
+Also, the kernel must have been built with modules enabled. If you are
+using a distribution kernel, there will be a package for the kernel you
+are running provided by your distribution.
 
---- 2.1 Building external modules
+An alternative is to use the "make" target "modules_prepare." This will
+make sure the kernel contains the information required. The target
+exists solely as a simple way to prepare a kernel source tree for
+building external modules.
 
-       Use the following command to build an external module:
+NOTE: "modules_prepare" will not build Module.symvers even if
+CONFIG_MODVERSIONS is set; therefore, a full kernel build needs to be
+executed to make module versioning work.
 
-               make -C <path-to-kernel> M=`pwd`
+--- 2.1 Command Syntax
 
-       For the running kernel use:
+       The command to build an external module is:
 
-               make -C /lib/modules/`uname -r`/build M=`pwd`
+               $ make -C <path_to_kernel_src> M=$PWD
 
-       For the above command to succeed, the kernel must have been
-       built with modules enabled.
+       The kbuild system knows that an external module is being built
+       due to the "M=<dir>" option given in the command.
 
-       To install the modules that were just built:
+       To build against the running kernel use:
 
-               make -C <path-to-kernel> M=`pwd` modules_install
+               $ make -C /lib/modules/`uname -r`/build M=$PWD
 
-       More complex examples will be shown later, the above should
-       be enough to get you started.
+       Then to install the module(s) just built, add the target
+       "modules_install" to the command:
 
---- 2.2 Available targets
+               $ make -C /lib/modules/`uname -r`/build M=$PWD modules_install
 
-       $KDIR refers to the path to the kernel source top-level directory
+--- 2.2 Options
 
-       make -C $KDIR M=`pwd`
-               Will build the module(s) located in current directory.
-               All output files will be located in the same directory
-               as the module source.
-               No attempts are made to update the kernel source, and it is
-               a precondition that a successful make has been executed
-               for the kernel.
+       ($KDIR refers to the path of the kernel source directory.)
 
-       make -C $KDIR M=`pwd` modules
-               The modules target is implied when no target is given.
-               Same functionality as if no target was specified.
-               See description above.
+       make -C $KDIR M=$PWD
 
-       make -C $KDIR M=`pwd` modules_install
-               Install the external module(s).
-               Installation default is in /lib/modules/<kernel-version>/extra,
-               but may be prefixed with INSTALL_MOD_PATH - see separate
-               chapter.
+       -C $KDIR
+               The directory where the kernel source is located.
+               "make" will actually change to the specified directory
+               when executing and will change back when finished.
 
-       make -C $KDIR M=`pwd` clean
-               Remove all generated files for the module - the kernel
-               source directory is not modified.
+       M=$PWD
+               Informs kbuild that an external module is being built.
+               The value given to "M" is the absolute path of the
+               directory where the external module (kbuild file) is
+               located.
 
-       make -C $KDIR M=`pwd` help
-               help will list the available target when building external
-               modules.
+--- 2.3 Targets
 
---- 2.3 Available options:
+       When building an external module, only a subset of the "make"
+       targets are available.
 
-       $KDIR refers to the path to the kernel source top-level directory
+       make -C $KDIR M=$PWD [target]
 
-       make -C $KDIR
-               Used to specify where to find the kernel source.
-               '$KDIR' represent the directory where the kernel source is.
-               Make will actually change directory to the specified directory
-               when executed but change back when finished.
+       The default will build the module(s) located in the current
+       directory, so a target does not need to be specified. All
+       output files will also be generated in this directory. No
+       attempts are made to update the kernel source, and it is a
+       precondition that a successful "make" has been executed for the
+       kernel.
 
-       make -C $KDIR M=`pwd`
-               M= is used to tell kbuild that an external module is
-               being built.
-               The option given to M= is the directory where the external
-               module (kbuild file) is located.
-               When an external module is being built only a subset of the
-               usual targets are available.
+       modules
+               The default target for external modules. It has the
+               same functionality as if no target was specified. See
+               description above.
 
-       make -C $KDIR SUBDIRS=`pwd`
-               Same as M=. The SUBDIRS= syntax is kept for backwards
-               compatibility.
+       modules_install
+               Install the external module(s). The default location is
+               /lib/modules/<kernel_release>/extra/, but a prefix may
+               be added with INSTALL_MOD_PATH (discussed in section 5).
 
---- 2.4 Preparing the kernel tree for module build
+       clean
+               Remove all generated files in the module directory only.
 
-       To make sure the kernel contains the information required to
-       build external modules the target 'modules_prepare' must be used.
-       'modules_prepare' exists solely as a simple way to prepare
-       a kernel source tree for building external modules.
-       Note: modules_prepare will not build Module.symvers even if
-       CONFIG_MODVERSIONS is set. Therefore a full kernel build
-       needs to be executed to make module versioning work.
+       help
+               List the available targets for external modules.
 
---- 2.5 Building separate files for a module
-       It is possible to build single files which are part of a module.
-       This works equally well for the kernel, a module and even for
-       external modules.
-       Examples (module foo.ko, consist of bar.o, baz.o):
-               make -C $KDIR M=`pwd` bar.lst
-               make -C $KDIR M=`pwd` bar.o
-               make -C $KDIR M=`pwd` foo.ko
-               make -C $KDIR M=`pwd` /
-
-
-=== 3. Example commands
-
-This example shows the actual commands to be executed when building
-an external module for the currently running kernel.
-In the example below, the distribution is supposed to use the
-facility to locate output files for a kernel compile in a different
-directory than the kernel source - but the examples will also work
-when the source and the output files are mixed in the same directory.
+--- 2.4 Building Separate Files
 
-# Kernel source
-/lib/modules/<kernel-version>/source -> /usr/src/linux-<version>
-
-# Output from kernel compile
-/lib/modules/<kernel-version>/build -> /usr/src/linux-<version>-up
-
-Change to the directory where the kbuild file is located and execute
-the following commands to build the module:
+       It is possible to build single files that are part of a module.
+       This works equally well for the kernel, a module, and even for
+       external modules.
 
-       cd /home/user/src/module
-       make -C /usr/src/`uname -r`/source            \
-               O=/lib/modules/`uname-r`/build        \
-               M=`pwd`
+       Example (The module foo.ko, consist of bar.o and baz.o):
+               make -C $KDIR M=$PWD bar.lst
+               make -C $KDIR M=$PWD baz.o
+               make -C $KDIR M=$PWD foo.ko
+               make -C $KDIR M=$PWD /
 
-Then, to install the module use the following command:
 
-       make -C /usr/src/`uname -r`/source            \
-               O=/lib/modules/`uname-r`/build        \
-               M=`pwd`                               \
-               modules_install
+=== 3. Creating a Kbuild File for an External Module
 
-If you look closely you will see that this is the same command as
-listed before - with the directories spelled out.
+In the last section we saw the command to build a module for the
+running kernel. The module is not actually built, however, because a
+build file is required. Contained in this file will be the name of
+the module(s) being built, along with the list of requisite source
+files. The file may be as simple as a single line:
 
-The above are rather long commands, and the following chapter
-lists a few tricks to make it all easier.
+       obj-m := <module_name>.o
 
+The kbuild system will build <module_name>.o from <module_name>.c,
+and, after linking, will result in the kernel module <module_name>.ko.
+The above line can be put in either a "Kbuild" file or a "Makefile."
+When the module is built from multiple sources, an additional line is
+needed listing the files:
 
-=== 4. Creating a kbuild file for an external module
+       <module_name>-y := <src1>.o <src2>.o ...
 
-kbuild is the build system for the kernel, and external modules
-must use kbuild to stay compatible with changes in the build system
-and to pick up the right flags to gcc etc.
+NOTE: Further documentation describing the syntax used by kbuild is
+located in Documentation/kbuild/makefiles.txt.
 
-The kbuild file used as input shall follow the syntax described
-in Documentation/kbuild/makefiles.txt. This chapter will introduce a few
-more tricks to be used when dealing with external modules.
+The examples below demonstrate how to create a build file for the
+module 8123.ko, which is built from the following files:
 
-In the following a Makefile will be created for a module with the
-following files:
        8123_if.c
        8123_if.h
        8123_pci.c
        8123_bin.o_shipped      <= Binary blob
 
---- 4.1 Shared Makefile for module and kernel
+--- 3.1 Shared Makefile
 
-       An external module always includes a wrapper Makefile supporting
-       building the module using 'make' with no arguments.
-       The Makefile provided will most likely include additional
-       functionality such as test targets etc. and this part shall
-       be filtered away from kbuild since it may impact kbuild if
-       name clashes occurs.
+       An external module always includes a wrapper makefile that
+       supports building the module using "make" with no arguments.
+       This target is not used by kbuild; it is only for convenience.
+       Additional functionality, such as test targets, can be included
+       but should be filtered out from kbuild due to possible name
+       clashes.
 
        Example 1:
                --> filename: Makefile
@@ -219,11 +189,11 @@ following files:
                8123-y := 8123_if.o 8123_pci.o 8123_bin.o
 
                else
-               # Normal Makefile
+               # normal makefile
+               KDIR ?= /lib/modules/`uname -r`/build
 
-               KERNELDIR := /lib/modules/`uname -r`/build
-               all::
-                       $(MAKE) -C $(KERNELDIR) M=`pwd` $@
+               default:
+                       $(MAKE) -C $(KDIR) M=$$PWD
 
                # Module specific targets
                genbin:
@@ -231,15 +201,20 @@ following files:
 
                endif
 
-       In example 1, the check for KERNELRELEASE is used to separate
-       the two parts of the Makefile. kbuild will only see the two
-       assignments whereas make will see everything except the two
-       kbuild assignments.
+       The check for KERNELRELEASE is used to separate the two parts
+       of the makefile. In the example, kbuild will only see the two
+       assignments, whereas "make" will see everything except these
+       two assignments. This is due to two passes made on the file:
+       the first pass is by the "make" instance run on the command
+       line; the second pass is by the kbuild system, which is
+       initiated by the parameterized "make" in the default target.
+
+--- 3.2 Separate Kbuild File and Makefile
 
-       In recent versions of the kernel, kbuild will look for a file named
-       Kbuild and as second option look for a file named Makefile.
-       Utilising the Kbuild file makes us split up the Makefile in example 1
-       into two files as shown in example 2:
+       In newer versions of the kernel, kbuild will first look for a
+       file named "Kbuild," and only if that is not found, will it
+       then look for a makefile. Utilizing a "Kbuild" file allows us
+       to split up the makefile from example 1 into two files:
 
        Example 2:
                --> filename: Kbuild
@@ -247,20 +222,21 @@ following files:
                8123-y := 8123_if.o 8123_pci.o 8123_bin.o
 
                --> filename: Makefile
-               KERNELDIR := /lib/modules/`uname -r`/build
-               all::
-                       $(MAKE) -C $(KERNELDIR) M=`pwd` $@
+               KDIR ?= /lib/modules/`uname -r`/build
+
+               default:
+                       $(MAKE) -C $(KDIR) M=$$PWD
 
                # Module specific targets
                genbin:
                        echo "X" > 8123_bin.o_shipped
 
+       The split in example 2 is questionable due to the simplicity of
+       each file; however, some external modules use makefiles
+       consisting of several hundred lines, and here it really pays
+       off to separate the kbuild part from the rest.
 
-       In example 2, we are down to two fairly simple files and for simple
-       files as used in this example the split is questionable. But some
-       external modules use Makefiles of several hundred lines and here it
-       really pays off to separate the kbuild part from the rest.
-       Example 3 shows a backward compatible version.
+       The next example shows a backward compatible version.
 
        Example 3:
                --> filename: Kbuild
@@ -269,13 +245,15 @@ following files:
 
                --> filename: Makefile
                ifneq ($(KERNELRELEASE),)
+               # kbuild part of makefile
                include Kbuild
+
                else
-               # Normal Makefile
+               # normal makefile
+               KDIR ?= /lib/modules/`uname -r`/build
 
-               KERNELDIR := /lib/modules/`uname -r`/build
-               all::
-                       $(MAKE) -C $(KERNELDIR) M=`pwd` $@
+               default:
+                       $(MAKE) -C $(KDIR) M=$$PWD
 
                # Module specific targets
                genbin:
@@ -283,260 +261,271 @@ following files:
 
                endif
 
-       The trick here is to include the Kbuild file from Makefile, so
-       if an older version of kbuild picks up the Makefile, the Kbuild
-       file will be included.
+       Here the "Kbuild" file is included from the makefile. This
+       allows an older version of kbuild, which only knows of
+       makefiles, to be used when the "make" and kbuild parts are
+       split into separate files.
 
---- 4.2 Binary blobs included in a module
+--- 3.3 Binary Blobs
 
-       Some external modules needs to include a .o as a blob. kbuild
-       has support for this, but requires the blob file to be named
-       <filename>_shipped. In our example the blob is named
-       8123_bin.o_shipped and when the kbuild rules kick in the file
-       8123_bin.o is created as a simple copy off the 8213_bin.o_shipped file
-       with the _shipped part stripped of the filename.
-       This allows the 8123_bin.o filename to be used in the assignment to
-       the module.
+       Some external modules need to include an object file as a blob.
+       kbuild has support for this, but requires the blob file to be
+       named <filename>_shipped. When the kbuild rules kick in, a copy
+       of <filename>_shipped is created with _shipped stripped off,
+       giving us <filename>. This shortened filename can be used in
+       the assignment to the module.
+
+       Throughout this section, 8123_bin.o_shipped has been used to
+       build the kernel module 8123.ko; it has been included as
+       8123_bin.o.
 
-       Example 4:
-               obj-m  := 8123.o
                8123-y := 8123_if.o 8123_pci.o 8123_bin.o
 
-       In example 4, there is no distinction between the ordinary .c/.h files
-       and the binary file. But kbuild will pick up different rules to create
-       the .o file.
+       Although there is no distinction between the ordinary source
+       files and the binary file, kbuild will pick up different rules
+       when creating the object file for the module.
+
+--- 3.4 Building Multiple Modules
 
+       kbuild supports building multiple modules with a single build
+       file. For example, if you wanted to build two modules, foo.ko
+       and bar.ko, the kbuild lines would be:
 
-=== 5. Include files
+               obj-m := foo.o bar.o
+               foo-y := <foo_srcs>
+               bar-y := <bar_srcs>
 
-Include files are a necessity when a .c file uses something from other .c
-files (not strictly in the sense of C, but if good programming practice is
-used). Any module that consists of more than one .c file will have a .h file
-for one of the .c files.
+       It is that simple!
 
-- If the .h file only describes a module internal interface, then the .h file
-  shall be placed in the same directory as the .c files.
-- If the .h files describe an interface used by other parts of the kernel
-  located in different directories, the .h files shall be located in
-  include/linux/ or other include/ directories as appropriate.
 
-One exception for this rule is larger subsystems that have their own directory
-under include/ such as include/scsi. Another exception is arch-specific
-.h files which are located under include/asm-$(ARCH)/*.
+=== 4. Include Files
 
-External modules have a tendency to locate include files in a separate include/
-directory and therefore need to deal with this in their kbuild file.
+Within the kernel, header files are kept in standard locations
+according to the following rule:
 
---- 5.1 How to include files from the kernel include dir
+       * If the header file only describes the internal interface of a
+         module, then the file is placed in the same directory as the
+         source files.
+       * If the header file describes an interface used by other parts
+         of the kernel that are located in different directories, then
+         the file is placed in include/linux/.
 
-       When a module needs to include a file from include/linux/, then one
-       just uses:
+         NOTE: There are two notable exceptions to this rule: larger
+         subsystems have their own directory under include/, such as
+         include/scsi; and architecture specific headers are located
+         under arch/$(ARCH)/include/.
 
-               #include <linux/modules.h>
+--- 4.1 Kernel Includes
 
-       kbuild will make sure to add options to gcc so the relevant
-       directories are searched.
-       Likewise for .h files placed in the same directory as the .c file.
+       To include a header file located under include/linux/, simply
+       use:
 
-               #include "8123_if.h"
+               #include <linux/module.h>
 
-       will do the job.
+       kbuild will add options to "gcc" so the relevant directories
+       are searched.
 
---- 5.2 External modules using an include/ dir
+--- 4.2 Single Subdirectory
 
-       External modules often locate their .h files in a separate include/
-       directory although this is not usual kernel style. When an external
-       module uses an include/ dir then kbuild needs to be told so.
-       The trick here is to use either EXTRA_CFLAGS (take effect for all .c
-       files) or CFLAGS_$F.o (take effect only for a single file).
+       External modules tend to place header files in a separate
+       include/ directory where their source is located, although this
+       is not the usual kernel style. To inform kbuild of the
+       directory, use either ccflags-y or CFLAGS_<filename>.o.
 
-       In our example, if we move 8123_if.h to a subdirectory named include/
-       the resulting Kbuild file would look like:
+       Using the example from section 3, if we moved 8123_if.h to a
+       subdirectory named include, the resulting kbuild file would
+       look like:
 
                --> filename: Kbuild
-               obj-m  := 8123.o
+               obj-m := 8123.o
 
-               EXTRA_CFLAGS := -Iinclude
+               ccflags-y := -Iinclude
                8123-y := 8123_if.o 8123_pci.o 8123_bin.o
 
-       Note that in the assignment there is no space between -I and the path.
-       This is a kbuild limitation:  there must be no space present.
+       Note that in the assignment there is no space between -I and
+       the path. This is a limitation of kbuild: there must be no
+       space present.
 
---- 5.3 External modules using several directories
-
-       If an external module does not follow the usual kernel style, but
-       decides to spread files over several directories, then kbuild can
-       handle this too.
+--- 4.3 Several Subdirectories
 
+       kbuild can handle files that are spread over several directories.
        Consider the following example:
 
-       |
-       +- src/complex_main.c
-       |   +- hal/hardwareif.c
-       |   +- hal/include/hardwareif.h
-       +- include/complex.h
-
-       To build a single module named complex.ko, we then need the following
+       .
+       |__ src
+       |   |__ complex_main.c
+       |   |__ hal
+       |       |__ hardwareif.c
+       |       |__ include
+       |           |__ hardwareif.h
+       |__ include
+           |__ complex.h
+
+       To build the module complex.ko, we then need the following
        kbuild file:
 
-       Kbuild:
+               --> filename: Kbuild
                obj-m := complex.o
                complex-y := src/complex_main.o
                complex-y += src/hal/hardwareif.o
 
-               EXTRA_CFLAGS := -I$(src)/include
-               EXTRA_CFLAGS += -I$(src)src/hal/include
+               ccflags-y := -I$(src)/include
+               ccflags-y += -I$(src)/src/hal/include
 
+       As you can see, kbuild knows how to handle object files located
+       in other directories. The trick is to specify the directory
+       relative to the kbuild file's location. That being said, this
+       is NOT recommended practice.
 
-       kbuild knows how to handle .o files located in another directory -
-       although this is NOT recommended practice. The syntax is to specify
-       the directory relative to the directory where the Kbuild file is
-       located.
+       For the header files, kbuild must be explicitly told where to
+       look. When kbuild executes, the current directory is always the
+       root of the kernel tree (the argument to "-C") and therefore an
+       absolute path is needed. $(src) provides the absolute path by
+       pointing to the directory where the currently executing kbuild
+       file is located.
 
-       To find the .h files, we have to explicitly tell kbuild where to look
-       for the .h files. When kbuild executes, the current directory is always
-       the root of the kernel tree (argument to -C) and therefore we have to
-       tell kbuild how to find the .h files using absolute paths.
-       $(src) will specify the absolute path to the directory where the
-       Kbuild file are located when being build as an external module.
-       Therefore -I$(src)/ is used to point out the directory of the Kbuild
-       file and any additional path are just appended.
 
-=== 6. Module installation
+=== 5. Module Installation
 
-Modules which are included in the kernel are installed in the directory:
+Modules which are included in the kernel are installed in the
+directory:
 
-       /lib/modules/$(KERNELRELEASE)/kernel
+       /lib/modules/$(KERNELRELEASE)/kernel/
 
-External modules are installed in the directory:
+And external modules are installed in:
 
-       /lib/modules/$(KERNELRELEASE)/extra
+       /lib/modules/$(KERNELRELEASE)/extra/
 
---- 6.1 INSTALL_MOD_PATH
+--- 5.1 INSTALL_MOD_PATH
 
-       Above are the default directories, but as always, some level of
-       customization is possible. One can prefix the path using the variable
-       INSTALL_MOD_PATH:
+       Above are the default directories but as always some level of
+       customization is possible. A prefix can be added to the
+       installation path using the variable INSTALL_MOD_PATH:
 
                $ make INSTALL_MOD_PATH=/frodo modules_install
-               => Install dir: /frodo/lib/modules/$(KERNELRELEASE)/kernel
-
-       INSTALL_MOD_PATH may be set as an ordinary shell variable or as in the
-       example above, can be specified on the command line when calling make.
-       INSTALL_MOD_PATH has effect both when installing modules included in
-       the kernel as well as when installing external modules.
+               => Install dir: /frodo/lib/modules/$(KERNELRELEASE)/kernel/
 
---- 6.2 INSTALL_MOD_DIR
+       INSTALL_MOD_PATH may be set as an ordinary shell variable or,
+       as shown above, can be specified on the command line when
+       calling "make." This has effect when installing both in-tree
+       and out-of-tree modules.
 
-       When installing external modules they are by default installed to a
-       directory under /lib/modules/$(KERNELRELEASE)/extra, but one may wish
-       to locate modules for a specific functionality in a separate
-       directory. For this purpose, one can use INSTALL_MOD_DIR to specify an
-       alternative name to 'extra'.
+--- 5.2 INSTALL_MOD_DIR
 
-               $ make INSTALL_MOD_DIR=gandalf -C KERNELDIR \
-                       M=`pwd` modules_install
-               => Install dir: /lib/modules/$(KERNELRELEASE)/gandalf
+       External modules are by default installed to a directory under
+       /lib/modules/$(KERNELRELEASE)/extra/, but you may wish to
+       locate modules for a specific functionality in a separate
+       directory. For this purpose, use INSTALL_MOD_DIR to specify an
+       alternative name to "extra."
 
+               $ make INSTALL_MOD_DIR=gandalf -C $KDIR \
+                      M=$PWD modules_install
+               => Install dir: /lib/modules/$(KERNELRELEASE)/gandalf/
 
-=== 7. Module versioning & Module.symvers
 
-Module versioning is enabled by the CONFIG_MODVERSIONS tag.
+=== 6. Module Versioning
 
-Module versioning is used as a simple ABI consistency check. The Module
-versioning creates a CRC value of the full prototype for an exported symbol and
-when a module is loaded/used then the CRC values contained in the kernel are
-compared with similar values in the module. If they are not equal, then the
-kernel refuses to load the module.
+Module versioning is enabled by the CONFIG_MODVERSIONS tag, and is used
+as a simple ABI consistency check. A CRC value of the full prototype
+for an exported symbol is created. When a module is loaded/used, the
+CRC values contained in the kernel are compared with similar values in
+the module; if they are not equal, the kernel refuses to load the
+module.
 
-Module.symvers contains a list of all exported symbols from a kernel build.
+Module.symvers contains a list of all exported symbols from a kernel
+build.
 
---- 7.1 Symbols from the kernel (vmlinux + modules)
+--- 6.1 Symbols From the Kernel (vmlinux + modules)
 
-       During a kernel build, a file named Module.symvers will be generated.
-       Module.symvers contains all exported symbols from the kernel and
-       compiled modules. For each symbols, the corresponding CRC value
-       is stored too.
+       During a kernel build, a file named Module.symvers will be
+       generated. Module.symvers contains all exported symbols from
+       the kernel and compiled modules. For each symbol, the
+       corresponding CRC value is also stored.
 
        The syntax of the Module.symvers file is:
-               <CRC>       <Symbol>           <module>
-       Sample:
+               <CRC>       <Symbol>           <module>
+
                0x2d036834  scsi_remove_host   drivers/scsi/scsi_mod
 
-       For a kernel build without CONFIG_MODVERSIONS enabled, the crc
-       would read: 0x00000000
+       For a kernel build without CONFIG_MODVERSIONS enabled, the CRC
+       would read 0x00000000.
 
        Module.symvers serves two purposes:
-       1) It lists all exported symbols both from vmlinux and all modules
-       2) It lists the CRC if CONFIG_MODVERSIONS is enabled
-
---- 7.2 Symbols and external modules
-
-       When building an external module, the build system needs access to
-       the symbols from the kernel to check if all external symbols are
-       defined. This is done in the MODPOST step and to obtain all
-       symbols, modpost reads Module.symvers from the kernel.
-       If a Module.symvers file is present in the directory where
-       the external module is being built, this file will be read too.
-       During the MODPOST step, a new Module.symvers file will be written
-       containing all exported symbols that were not defined in the kernel.
-
---- 7.3 Symbols from another external module
-
-       Sometimes, an external module uses exported symbols from another
-       external module. Kbuild needs to have full knowledge on all symbols
-       to avoid spitting out warnings about undefined symbols.
-       Three solutions exist to let kbuild know all symbols of more than
-       one external module.
-       The method with a top-level kbuild file is recommended but may be
-       impractical in certain situations.
-
-       Use a top-level Kbuild file
-               If you have two modules: 'foo' and 'bar', and 'foo' needs
-               symbols from 'bar', then one can use a common top-level kbuild
-               file so both modules are compiled in same build.
-
-               Consider following directory layout:
-               ./foo/ <= contains the foo module
-               ./bar/ <= contains the bar module
-               The top-level Kbuild file would then look like:
-
-               #./Kbuild: (this file may also be named Makefile)
+       1) It lists all exported symbols from vmlinux and all modules.
+       2) It lists the CRC if CONFIG_MODVERSIONS is enabled.
+
+--- 6.2 Symbols and External Modules
+
+       When building an external module, the build system needs access
+       to the symbols from the kernel to check if all external symbols
+       are defined. This is done in the MODPOST step. modpost obtains
+       the symbols by reading Module.symvers from the kernel source
+       tree. If a Module.symvers file is present in the directory
+       where the external module is being built, this file will be
+       read too. During the MODPOST step, a new Module.symvers file
+       will be written containing all exported symbols that were not
+       defined in the kernel.
+
+--- 6.3 Symbols From Another External Module
+
+       Sometimes, an external module uses exported symbols from
+       another external module. kbuild needs to have full knowledge of
+       all symbols to avoid spitting out warnings about undefined
+       symbols. Three solutions exist for this situation.
+
+       NOTE: The method with a top-level kbuild file is recommended
+       but may be impractical in certain situations.
+
+       Use a top-level kbuild file
+               If you have two modules, foo.ko and bar.ko, where
+               foo.ko needs symbols from bar.ko, you can use a
+               common top-level kbuild file so both modules are
+               compiled in the same build. Consider the following
+               directory layout:
+
+               ./foo/ <= contains foo.ko
+               ./bar/ <= contains bar.ko
+
+               The top-level kbuild file would then look like:
+
+               #./Kbuild (or ./Makefile):
                        obj-y := foo/ bar/
 
-               Executing:
-                       make -C $KDIR M=`pwd`
+               And executing
+
+                       $ make -C $KDIR M=$PWD
 
-               will then do the expected and compile both modules with full
-               knowledge on symbols from both modules.
+               will then do the expected and compile both modules with
+               full knowledge of symbols from either module.
 
        Use an extra Module.symvers file
-               When an external module is built, a Module.symvers file is
-               generated containing all exported symbols which are not
-               defined in the kernel.
-               To get access to symbols from module 'bar', one can copy the
-               Module.symvers file from the compilation of the 'bar' module
-               to the directory where the 'foo' module is built.
-               During the module build, kbuild will read the Module.symvers
-               file in the directory of the external module and when the
-               build is finished, a new Module.symvers file is created
-               containing the sum of all symbols defined and not part of the
-               kernel.
-
-       Use make variable KBUILD_EXTRA_SYMBOLS in the Makefile
-               If it is impractical to copy Module.symvers from another
-               module, you can assign a space separated list of files to
-               KBUILD_EXTRA_SYMBOLS in your Makfile. These files will be
-               loaded by modpost during the initialisation of its symbol
-               tables.
-
-=== 8. Tips & Tricks
-
---- 8.1 Testing for CONFIG_FOO_BAR
-
-       Modules often need to check for certain CONFIG_ options to decide if
-       a specific feature shall be included in the module. When kbuild is used
-       this is done by referencing the CONFIG_ variable directly.
+               When an external module is built, a Module.symvers file
+               is generated containing all exported symbols which are
+               not defined in the kernel. To get access to symbols
+               from bar.ko, copy the Module.symvers file from the
+               compilation of bar.ko to the directory where foo.ko is
+               built. During the module build, kbuild will read the
+               Module.symvers file in the directory of the external
+               module, and when the build is finished, a new
+               Module.symvers file is created containing the sum of
+               all symbols defined and not part of the kernel.
+
+       Use "make" variable KBUILD_EXTRA_SYMBOLS
+               If it is impractical to copy Module.symvers from
+               another module, you can assign a space separated list
+               of files to KBUILD_EXTRA_SYMBOLS in your build file.
+               These files will be loaded by modpost during the
+               initialization of its symbol tables.
+
+
+=== 7. Tips & Tricks
+
+--- 7.1 Testing for CONFIG_FOO_BAR
+
+       Modules often need to check for certain CONFIG_ options to
+       decide if a specific feature is included in the module. In
+       kbuild this is done by referencing the CONFIG_ variable
+       directly.
 
                #fs/ext2/Makefile
                obj-$(CONFIG_EXT2_FS) += ext2.o
@@ -544,9 +533,9 @@ Module.symvers contains a list of all exported symbols from a kernel build.
                ext2-y := balloc.o bitmap.o dir.o
                ext2-$(CONFIG_EXT2_FS_XATTR) += xattr.o
 
-       External modules have traditionally used grep to check for specific
-       CONFIG_ settings directly in .config. This usage is broken.
-       As introduced before, external modules shall use kbuild when building
-       and therefore can use the same methods as in-kernel modules when
-       testing for CONFIG_ definitions.
+       External modules have traditionally used "grep" to check for
+       specific CONFIG_ settings directly in .config. This usage is
+       broken. As introduced before, external modules should use
+       kbuild for building and can therefore use the same methods as
+       in-tree modules when testing for CONFIG_ definitions.
 
diff --git a/Kbuild b/Kbuild
index b00037a..2114113 100644 (file)
--- a/Kbuild
+++ b/Kbuild
@@ -95,5 +95,5 @@ PHONY += missing-syscalls
 missing-syscalls: scripts/checksyscalls.sh FORCE
        $(call cmd,syscalls)
 
-# Delete all targets during make clean
-clean-files := $(addprefix $(objtree)/,$(filter-out $(bounds-file) $(offsets-file),$(targets)))
+# Keep these two files during make clean
+no-clean-files := $(bounds-file) $(offsets-file)
diff --git a/Kconfig b/Kconfig
new file mode 100644 (file)
index 0000000..c13f48d
--- /dev/null
+++ b/Kconfig
@@ -0,0 +1,11 @@
+#
+# For a description of the syntax of this configuration file,
+# see Documentation/kbuild/kconfig-language.txt.
+#
+mainmenu "Linux/$ARCH $KERNELVERSION Kernel Configuration"
+
+config SRCARCH
+       string
+       option env="SRCARCH"
+
+source "arch/$SRCARCH/Kconfig"
index d0c2206..cb8b580 100644 (file)
@@ -1613,7 +1613,7 @@ F:        drivers/platform/x86/classmate-laptop.c
 COCCINELLE/Semantic Patches (SmPL)
 M:     Julia Lawall <julia@diku.dk>
 M:     Gilles Muller <Gilles.Muller@lip6.fr>
-M:     Nicolas Palix <npalix@diku.dk>
+M:     Nicolas Palix <npalix.work@gmail.com>
 L:     cocci@diku.dk (moderated for non-subscribers)
 W:     http://coccinelle.lip6.fr/
 S:     Supported
@@ -6595,11 +6595,25 @@ T:      git git://git.kernel.org/pub/scm/linux/kernel/git/mjg59/platform-drivers-x86.
 S:     Maintained
 F:     drivers/platform/x86
 
+XEN PCI SUBSYSTEM
+M:     Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
+L:     xen-devel@lists.xensource.com
+S:     Supported
+F:     arch/x86/pci/*xen*
+F:     drivers/pci/*xen*
+
+XEN SWIOTLB SUBSYSTEM
+M:     Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
+L:     xen-devel@lists.xensource.com
+S:     Supported
+F:     arch/x86/xen/*swiotlb*
+F:     drivers/xen/*swiotlb*
+
 XEN HYPERVISOR INTERFACE
-M:     Jeremy Fitzhardinge <jeremy@xensource.com>
-M:     Chris Wright <chrisw@sous-sol.org>
+M:     Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
+M:     Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
+L:     xen-devel@lists.xen.org
 L:     virtualization@lists.osdl.org
-L:     xen-devel@lists.xensource.com
 S:     Supported
 F:     arch/x86/xen/
 F:     drivers/*/xen-*front.c
index 3e43805..519db43 100644 (file)
--- a/Makefile
+++ b/Makefile
@@ -204,6 +204,9 @@ ifeq ($(ARCH),x86_64)
 endif
 
 # Additional ARCH settings for sparc
+ifeq ($(ARCH),sparc32)
+       SRCARCH := sparc
+endif
 ifeq ($(ARCH),sparc64)
        SRCARCH := sparc
 endif
@@ -1137,21 +1140,13 @@ MRPROPER_FILES += .config .config.old .version .old_version             \
 #
 clean: rm-dirs  := $(CLEAN_DIRS)
 clean: rm-files := $(CLEAN_FILES)
-clean-dirs      := $(addprefix _clean_,$(srctree) $(vmlinux-alldirs) Documentation)
+clean-dirs      := $(addprefix _clean_, . $(vmlinux-alldirs) Documentation)
 
 PHONY += $(clean-dirs) clean archclean
 $(clean-dirs):
        $(Q)$(MAKE) $(clean)=$(patsubst _clean_%,%,$@)
 
-clean: archclean $(clean-dirs)
-       $(call cmd,rmdirs)
-       $(call cmd,rmfiles)
-       @find . $(RCS_FIND_IGNORE) \
-               \( -name '*.[oas]' -o -name '*.ko' -o -name '.*.cmd' \
-               -o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
-               -o -name '*.symtypes' -o -name 'modules.order' \
-               -o -name modules.builtin -o -name '.tmp_*.o.*' \
-               -o -name '*.gcno' \) -type f -print | xargs rm -f
+clean: archclean
 
 # mrproper - Delete all generated files, including .config
 #
@@ -1352,16 +1347,7 @@ $(clean-dirs):
        $(Q)$(MAKE) $(clean)=$(patsubst _clean_%,%,$@)
 
 clean: rm-dirs := $(MODVERDIR)
-clean: rm-files := $(KBUILD_EXTMOD)/Module.symvers \
-                   $(KBUILD_EXTMOD)/modules.order \
-                   $(KBUILD_EXTMOD)/modules.builtin
-clean: $(clean-dirs)
-       $(call cmd,rmdirs)
-       $(call cmd,rmfiles)
-       @find $(KBUILD_EXTMOD) $(RCS_FIND_IGNORE) \
-               \( -name '*.[oas]' -o -name '*.ko' -o -name '.*.cmd' \
-               -o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
-               -o -name '*.gcno' \) -type f -print | xargs rm -f
+clean: rm-files := $(KBUILD_EXTMOD)/Module.symvers
 
 help:
        @echo  '  Building external modules.'
@@ -1378,6 +1364,16 @@ prepare: ;
 scripts: ;
 endif # KBUILD_EXTMOD
 
+clean: $(clean-dirs)
+       $(call cmd,rmdirs)
+       $(call cmd,rmfiles)
+       @find $(or $(KBUILD_EXTMOD), .) $(RCS_FIND_IGNORE) \
+               \( -name '*.[oas]' -o -name '*.ko' -o -name '.*.cmd' \
+               -o -name '.*.d' -o -name '.*.tmp' -o -name '*.mod.c' \
+               -o -name '*.symtypes' -o -name 'modules.order' \
+               -o -name modules.builtin -o -name '.tmp_*.o.*' \
+               -o -name '*.gcno' \) -type f -print | xargs rm -f
+
 # Generate tags for editors
 # ---------------------------------------------------------------------------
 quiet_cmd_tags = GEN     $@
diff --git a/README b/README
index 737838f..1b81d28 100644 (file)
--- a/README
+++ b/README
@@ -166,6 +166,7 @@ CONFIGURING the kernel:
  - Alternate configuration commands are:
        "make config"      Plain text interface.
        "make menuconfig"  Text based color menus, radiolists & dialogs.
+       "make nconfig"     Enhanced text based color menus.
        "make xconfig"     X windows (Qt) based configuration tool.
        "make gconfig"     X windows (Gtk) based configuration tool.
        "make oldconfig"   Default all questions based on the contents of
index 53d7f61..8bf0fa6 100644 (file)
@@ -42,6 +42,20 @@ config KPROBES
          for kernel debugging, non-intrusive instrumentation and testing.
          If in doubt, say "N".
 
+config JUMP_LABEL
+       bool "Optimize trace point call sites"
+       depends on HAVE_ARCH_JUMP_LABEL
+       help
+         If it is detected that the compiler has support for "asm goto",
+        the kernel will compile trace point locations with just a
+        nop instruction. When trace points are enabled, the nop will
+        be converted to a jump to the trace function. This technique
+        lowers overhead and stress on the branch prediction of the
+        processor.
+
+        On i386, options added to the compiler flags may increase
+        the size of the kernel slightly.
+
 config OPTPROBES
        def_bool y
        depends on KPROBES && HAVE_OPTPROBES
index 28f93a6..943fe69 100644 (file)
@@ -1,7 +1,3 @@
-#
-# For a description of the syntax of this configuration file,
-# see Documentation/kbuild/kconfig-language.txt.
-#
 config ALPHA
        bool
        default y
index bf7273f..a19a526 100644 (file)
@@ -1,10 +1,3 @@
-#
-# For a description of the syntax of this configuration file,
-# see Documentation/kbuild/kconfig-language.txt.
-#
-
-mainmenu "Linux Kernel Configuration"
-
 config ARM
        bool
        default y
@@ -727,9 +720,11 @@ config ARCH_S5PC100
 config ARCH_S5PV210
        bool "Samsung S5PV210/S5PC110"
        select CPU_V7
+       select ARCH_SPARSEMEM_ENABLE
        select GENERIC_GPIO
        select HAVE_CLK
        select ARM_L1_CACHE_SHIFT_6
+       select ARCH_HAS_CPUFREQ
        select ARCH_USES_GETTIMEOFFSET
        select HAVE_S3C2410_I2C
        select HAVE_S3C_RTC
@@ -740,9 +735,13 @@ config ARCH_S5PV210
 config ARCH_S5PV310
        bool "Samsung S5PV310/S5PC210"
        select CPU_V7
+       select ARCH_SPARSEMEM_ENABLE
        select GENERIC_GPIO
        select HAVE_CLK
        select GENERIC_CLOCKEVENTS
+       select HAVE_S3C_RTC
+       select HAVE_S3C2410_I2C
+       select HAVE_S3C2410_WATCHDOG
        help
          Samsung S5PV310 series based systems
 
@@ -1669,6 +1668,12 @@ if ARCH_HAS_CPUFREQ
 
 source "drivers/cpufreq/Kconfig"
 
+config CPU_FREQ_IMX
+       tristate "CPUfreq driver for i.MX CPUs"
+       depends on ARCH_MXC && CPU_FREQ
+       help
+         This enables the CPUfreq driver for i.MX CPUs.
+
 config CPU_FREQ_SA1100
        bool
 
index 163cfee..5c7a872 100644 (file)
@@ -82,6 +82,7 @@ CONFIG_FEC=y
 CONFIG_INPUT_FF_MEMLESS=m
 # CONFIG_INPUT_MOUSEDEV_PSAUX is not set
 CONFIG_INPUT_EVDEV=y
+CONFIG_KEYBOARD_GPIO=y
 CONFIG_INPUT_EVBUG=m
 CONFIG_MOUSE_PS2=m
 CONFIG_MOUSE_PS2_ELANTECH=y
index 6bcba48..cc42d5f 100644 (file)
@@ -21,9 +21,6 @@
 #define __ASM_ARM_HARDWARE_L2X0_H
 
 #define L2X0_CACHE_ID                  0x000
-#define   L2X0_CACHE_ID_PART_MASK      (0xf << 6)
-#define   L2X0_CACHE_ID_PART_L210      (1 << 6)
-#define   L2X0_CACHE_ID_PART_L310      (3 << 6)
 #define L2X0_CACHE_TYPE                        0x004
 #define L2X0_CTRL                      0x100
 #define L2X0_AUX_CTRL                  0x104
 #define L2X0_LINE_DATA                 0xF10
 #define L2X0_LINE_TAG                  0xF30
 #define L2X0_DEBUG_CTRL                        0xF40
+#define L2X0_PREFETCH_CTRL             0xF60
+#define L2X0_POWER_CTRL                        0xF80
+#define   L2X0_DYNAMIC_CLK_GATING_EN   (1 << 1)
+#define   L2X0_STNDBY_MODE_EN          (1 << 0)
+
+/* Registers shifts and masks */
+#define L2X0_CACHE_ID_PART_MASK                (0xf << 6)
+#define L2X0_CACHE_ID_PART_L210                (1 << 6)
+#define L2X0_CACHE_ID_PART_L310                (3 << 6)
+#define L2X0_AUX_CTRL_WAY_SIZE_MASK    (0x3 << 17)
 
 #ifndef __ASSEMBLY__
 extern void __init l2x0_init(void __iomem *base, __u32 aux_val, __u32 aux_mask);
index 0826599..48066ce 100644 (file)
@@ -70,7 +70,8 @@ extern int kgdb_fault_expected;
 #define _GP_REGS               16
 #define _FP_REGS               8
 #define _EXTRA_REGS            2
-#define DBG_MAX_REG_NUM                (_GP_REGS + (_FP_REGS * 3) + _EXTRA_REGS)
+#define GDB_MAX_REGS           (_GP_REGS + (_FP_REGS * 3) + _EXTRA_REGS)
+#define DBG_MAX_REG_NUM                (_GP_REGS + _FP_REGS + _EXTRA_REGS)
 
 #define KGDB_MAX_NO_CPUS       1
 #define BUFMAX                 400
@@ -93,7 +94,7 @@ extern int kgdb_fault_expected;
 #define _SPT                   13
 #define _LR                    14
 #define _PC                    15
-#define _CPSR                  (DBG_MAX_REG_NUM - 1)
+#define _CPSR                  (GDB_MAX_REGS - 1)
 
 /*
  * So that we can denote the end of a frame for tracing,
index fdbc43b..b8da2e4 100644 (file)
@@ -1,13 +1,6 @@
 #ifndef _ASM_ARM_MEMBLOCK_H
 #define _ASM_ARM_MEMBLOCK_H
 
-#ifdef CONFIG_MMU
-extern phys_addr_t lowmem_end_addr;
-#define MEMBLOCK_REAL_LIMIT    lowmem_end_addr
-#else
-#define MEMBLOCK_REAL_LIMIT    0
-#endif
-
 struct meminfo;
 struct machine_desc;
 
index 25f76ba..fc19009 100644 (file)
@@ -25,6 +25,9 @@ struct outer_cache_fns {
        void (*inv_range)(unsigned long, unsigned long);
        void (*clean_range)(unsigned long, unsigned long);
        void (*flush_range)(unsigned long, unsigned long);
+       void (*flush_all)(void);
+       void (*inv_all)(void);
+       void (*disable)(void);
 #ifdef CONFIG_OUTER_CACHE_SYNC
        void (*sync)(void);
 #endif
@@ -50,6 +53,24 @@ static inline void outer_flush_range(unsigned long start, unsigned long end)
                outer_cache.flush_range(start, end);
 }
 
+static inline void outer_flush_all(void)
+{
+       if (outer_cache.flush_all)
+               outer_cache.flush_all();
+}
+
+static inline void outer_inv_all(void)
+{
+       if (outer_cache.inv_all)
+               outer_cache.inv_all();
+}
+
+static inline void outer_disable(void)
+{
+       if (outer_cache.disable)
+               outer_cache.disable();
+}
+
 #else
 
 static inline void outer_inv_range(unsigned long start, unsigned long end)
@@ -58,6 +79,9 @@ static inline void outer_clean_range(unsigned long start, unsigned long end)
 { }
 static inline void outer_flush_range(unsigned long start, unsigned long end)
 { }
+static inline void outer_flush_all(void) { }
+static inline void outer_inv_all(void) { }
+static inline void outer_disable(void) { }
 
 #endif
 
index d6e8b4d..778c2f7 100644 (file)
@@ -79,7 +79,7 @@ sleeping_thread_to_gdb_regs(unsigned long *gdb_regs, struct task_struct *task)
                return;
 
        /* Initialize to zero */
-       for (regno = 0; regno < DBG_MAX_REG_NUM; regno++)
+       for (regno = 0; regno < GDB_MAX_REGS; regno++)
                gdb_regs[regno] = 0;
 
        /* Otherwise, we have only some registers from switch_to() */
index 1fc74cb..3a8fd51 100644 (file)
@@ -78,7 +78,10 @@ void machine_kexec(struct kimage *image)
        local_fiq_disable();
        setup_mm_for_reboot(0); /* mode is not used, so just pass 0*/
        flush_cache_all();
+       outer_flush_all();
+       outer_disable();
        cpu_proc_fin();
+       outer_inv_all();
        flush_cache_all();
        cpu_reset(reboot_code_buffer_phys);
 }