Hi all,
This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
Changes since 20090105:
New tree:
squashfs
Undropped tree:
usb
staging
Dropped trees (temporarily):
rr (build problem)
semaphore-removal (due to unfixed conflicts against Linus' tree)
cpu_alloc (build problem)
audit (difficult conflicts)
The driver-core tree lost its 2 conflicts.
The usb tree lost its 2 conflicts and its build failure.
The pci tree gained a conflict against Linus' tree.
The mtd tree lost 3 conflicts.
The rr tree lost 4 conflicts but gained another against the ftrace tree
and a build failure and so was dropped.
The mfd tree gained 2 conflicts against the usb tree.
The iommu tree gained a conflict against the tip-core tree.
The staging tree lost its 7 conflicts.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES) and
i386, sparc and sparc64 defconfig.
Below is a summary of the state of the merge.
We are up to 131 trees (counting Linus' and 15 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell [email protected]
http://www.canb.auug.org.au/~sfr/
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
CONFLICT (content): Merge conflict in drivers/char/tty_audit.c
CONFLICT (content): Merge conflict in kernel/auditsc.c
Merging dwmw2/master
Merging arm/devel
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging mips/mips-for-linux-next
Merging parisc/master
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging pxa/for-next
Merging s390/features
Merging sh/master
Merging sparc/master
Merging x86/auto-x86-next
Merging xtensa/master
Merging quilt/driver-core
Merging quilt/usb
Merging tip-core/auto-core-next
Merging cpus4096/auto-cpus4096-next
CONFLICT (content): Merge conflict in kernel/rcuclassic.c
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
CONFLICT (content): Merge conflict in kernel/time/tick-common.c
Merging pci/linux-next
CONFLICT (content): Merge conflict in drivers/pci/hotplug/acpiphp_glue.c
Merging quilt/device-mapper
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
Merging nfsd/nfsd-next
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
Merging dlm/next
Merging scsi/master
CONFLICT (content): Merge conflict in drivers/scsi/scsi_ioctl.c
Merging ocfs2/linux-next
Merging ext4/next
CONFLICT (content): Merge conflict in fs/ext4/ialloc.c
Merging async_tx/next
Applying: net: async_tx merge fix
Merging udf/for_next
Merging net/master
Merging mtd/master
CONFLICT (content): Merge conflict in drivers/mtd/devices/m25p80.c
CONFLICT (content): Merge conflict in drivers/mtd/devices/mtd_dataflash.c
Merging wireless/master
Merging crypto/master
Merging vfs/for-next
Merging sound/for-next
Merging cpufreq/next
Merging v9fs/for-next
Merging quilt/rr
CONFLICT (content): Merge conflict in init/main.c
$ git reset --hard HEAD^
Merging cifs/master
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging bkl-removal/bkl-removal
CONFLICT (content): Merge conflict in fs/ioctl.c
Merging ubifs/linux-next
Merging lsm/for-next
Merging block/for-next
Merging embedded/master
Merging firmware/master
CONFLICT (content): Merge conflict in drivers/net/starfire.c
CONFLICT (content): Merge conflict in drivers/net/tg3.c
CONFLICT (content): Merge conflict in firmware/Makefile
CONFLICT (content): Merge conflict in firmware/WHENCE
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging kmemcheck/auto-kmemcheck-next
CONFLICT (content): Merge conflict in MAINTAINERS
Merging generic-ipi/auto-generic-ipi-next
Merging mfd/for-next
CONFLICT (content): Merge conflict in drivers/i2c/chips/Kconfig
CONFLICT (content): Merge conflict in drivers/i2c/chips/Makefile
Merging hdlc/hdlc-next
Merging drm/drm-next
Merging voltage/for-next
Merging security-testing/next
CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt
Merging lblnet/master
Merging quilt/ttydev
Merging agp/agp-next
Merging oprofile/auto-oprofile-next
Merging fastboot/auto-fastboot-next
Merging sparseirq/auto-sparseirq-next
Merging iommu/auto-iommu-next
CONFLICT (content): Merge conflict in lib/swiotlb.c
Merging uwb/for-upstream
Merging watchdog/master
Merging proc/proc
Merging bdev/master
Merging dwmw2-iommu/master
CONFLICT (content): Merge conflict in drivers/pci/intel-iommu.c
CONFLICT (content): Merge conflict in include/linux/dma_remapping.h
Merging cputime/cputime
Merging osd/linux-next
Merging fatfs/master
Merging fuse/for-next
Merging jc_docs/docs-next
Merging nommu/master
CONFLICT (content): Merge conflict in kernel/fork.c
Merging trivial/for-next
Merging squashfs/master
Merging quilt/staging
Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
>
> Dropped trees (temporarily):
> rr (build problem)
> semaphore-removal (due to unfixed conflicts against Linus' tree)
> cpu_alloc (build problem)
> audit (difficult conflicts)
>
>
> The mtd tree lost 3 conflicts.
drivers/built-in.o: In function `lpddr_probe':
(.text+0x95ddc): undefined reference to `lpddr_cmdset'
with
# CONFIG_MTD_LPDDR is not set
CONFIG_MTD_QINFO_PROBE=y
There appears to be too little control/coordination between those
two kconfig symbols. Surely one of them (MTD_QINFO_PROBE) should
depend on the other (MTD_LPDDR). And why even build 2 modules
when MTD_QINFO_PROBE is enabled? Why not combine the code into
one module?
--
~Randy
Hi Randy,
> # CONFIG_MTD_LPDDR is not set
> CONFIG_MTD_QINFO_PROBE=y
>
> There appears to be too little control/coordination between those
> two kconfig symbols. Surely one of them (MTD_QINFO_PROBE) should
> depend on the other (MTD_LPDDR). And why even build 2 modules
> when MTD_QINFO_PROBE is enabled? Why not combine the code into
> one module?
Thanks a lot for good finding. Here is a fix for the problem.
About combining: it is assumed to have one QINFO probing module for several
kinds of LPDDR command set drivers. If we combine two modules into
one it would make further extension rather hard. So it is better to have
two modules.
To fix a problem I just added dependency in Kconfig file.
This temporary fix which will work until we have just one cmdset module.
In near future we will make a fix which parse command set types
and select proper driver according to device type.
Thanks,
Alexey
Signed-off-by: Alexey Korolev <[email protected]>
---
diff --git a/drivers/mtd/lpddr/Kconfig b/drivers/mtd/lpddr/Kconfig
index acd4ea9..5a401d8 100644
--- a/drivers/mtd/lpddr/Kconfig
+++ b/drivers/mtd/lpddr/Kconfig
@@ -12,6 +12,7 @@ config MTD_LPDDR
DDR memories, intended for battery-operated systems.
config MTD_QINFO_PROBE
+ depends on MTD_LPDDR
tristate "Detect flash chips by QINFO probe"
help
Device Information for LPDDR chips is offered through the Overlay
Alexey Korolev wrote:
> Hi Randy,
>
>> # CONFIG_MTD_LPDDR is not set
>> CONFIG_MTD_QINFO_PROBE=y
>>
>> There appears to be too little control/coordination between those
>> two kconfig symbols. Surely one of them (MTD_QINFO_PROBE) should
>> depend on the other (MTD_LPDDR). And why even build 2 modules
>> when MTD_QINFO_PROBE is enabled? Why not combine the code into
>> one module?
> Thanks a lot for good finding. Here is a fix for the problem.
>
> About combining: it is assumed to have one QINFO probing module for several
> kinds of LPDDR command set drivers. If we combine two modules into
> one it would make further extension rather hard. So it is better to have
> two modules.
> To fix a problem I just added dependency in Kconfig file.
> This temporary fix which will work until we have just one cmdset module.
> In near future we will make a fix which parse command set types
> and select proper driver according to device type.
>
> Thanks,
> Alexey
>
> Signed-off-by: Alexey Korolev <[email protected]>
Acked-by: Randy Dunlap <[email protected]>
Thanks.
> ---
> diff --git a/drivers/mtd/lpddr/Kconfig b/drivers/mtd/lpddr/Kconfig
> index acd4ea9..5a401d8 100644
> --- a/drivers/mtd/lpddr/Kconfig
> +++ b/drivers/mtd/lpddr/Kconfig
> @@ -12,6 +12,7 @@ config MTD_LPDDR
> DDR memories, intended for battery-operated systems.
>
> config MTD_QINFO_PROBE
> + depends on MTD_LPDDR
> tristate "Detect flash chips by QINFO probe"
> help
> Device Information for LPDDR chips is offered through the Overlay
>
>
--
~Randy
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
wimax build fails when CONFIG_INPUT=n:
net/built-in.o: In function `wimax_report_rfkill_hw':
(.text+0x1540c0): undefined reference to `input_event'
net/built-in.o: In function `wimax_rfkill_rm':
(.text+0x1541b1): undefined reference to `input_unregister_device'
net/built-in.o: In function `wimax_rfkill_add':
(.text+0x1542db): undefined reference to `input_allocate_device'
net/built-in.o: In function `wimax_rfkill_add':
(.text+0x154373): undefined reference to `input_register_device'
net/built-in.o: In function `wimax_rfkill_add':
(.text+0x15440c): undefined reference to `input_unregister_device'
net/built-in.o: In function `wimax_rfkill_add':
(.text+0x154428): undefined reference to `input_free_device'
Also, this warning needs to be fixed:
linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90 forbids mixed declarations and code
---
~Randy
On Tuesday 06 January 2009, Randy Dunlap wrote:
> On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> > Hi all,
> >
> > This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
> >
> > Changes since 20090105:
>
> wimax build fails when CONFIG_INPUT=n:
Ops -- my fault -- working on a fix.
> Also, this warning needs to be fixed:
>
> linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90 forbids
> mixed declarations and code
Will fix too.
Thanks Randy,
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
drivers/staging/comedi/kcomedilib/built-in.o: In function `comedi_unmap':
(.text+0x481): multiple definition of `comedi_unmap'
drivers/staging/comedi/comedi.o:(.text+0xe5): first defined here
---
~Randy
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
drivers/staging/altpciechdma/altpciechdma.c: In function 'ape_sg_to_chdma_table':
drivers/staging/altpciechdma/altpciechdma.c:430: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'dma_addr_t'
drivers/staging/altpciechdma/altpciechdma.c:434: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'dma_addr_t'
drivers/staging/altpciechdma/altpciechdma.c:450: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'dma_addr_t'
drivers/staging/altpciechdma/altpciechdma.c:451: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'dma_addr_t'
drivers/staging/altpciechdma/altpciechdma.c: In function 'dma_test':
drivers/staging/altpciechdma/altpciechdma.c:548: warning: assignment makes integer from pointer without a cast
drivers/staging/altpciechdma/altpciechdma.c: In function 'probe':
drivers/staging/altpciechdma/altpciechdma.c:931: warning: label 'err_rev' defined but not used
drivers/staging/altpciechdma/altpciechdma.c:914: warning: label 'err_cdev' defined but not used
drivers/staging/altpciechdma/altpciechdma.c: At top level:
drivers/staging/altpciechdma/altpciechdma.c:416: warning: 'ape_sg_to_chdma_table' defined but not used
---
~Randy
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
drivers/staging/meilhaus/me1000.o: In function `cleanup_module':
(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
drivers/staging/meilhaus/me1000.o: In function `init_module':
(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlock_lock':
(.text+0x2470): multiple definition of `me_dlock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2470): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_deinit':
(.text+0x2320): multiple definition of `me_dlist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2320): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_get_device':
(.text+0x2380): multiple definition of `me_dlist_get_device'
drivers/staging/meilhaus/me1000.o:(.text+0x2380): first defined here
drivers/staging/meilhaus/me4600.o: In function `cleanup_module':
(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_add_subdevice_tail':
(.text+0x2940): multiple definition of `me_slist_add_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2b60): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_deinit':
(.text+0x2980): multiple definition of `me_slist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2ba0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlock_enter':
(.text+0x2400): multiple definition of `me_dlock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2400): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slock_deinit':
(.text+0x2be0): multiple definition of `me_slock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2e00): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slock_lock':
(.text+0x2b60): multiple definition of `me_slock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2d80): first defined here
drivers/staging/meilhaus/me4600.o: In function `init_module':
(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_query_number_subdevices':
(.text+0x2920): multiple definition of `me_slist_query_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b40): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_init':
(.text+0x2960): multiple definition of `me_slist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2b80): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlock_deinit':
(.text+0x2440): multiple definition of `me_dlock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2440): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_subdevice_deinit':
(.text+0x27b0): multiple definition of `me_subdevice_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x29d0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_init':
(.text+0x2300): multiple definition of `me_dlist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2300): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_get_subdevice':
(.text+0x2aa0): multiple definition of `me_slist_get_subdevice'
drivers/staging/meilhaus/me1000.o:(.text+0x2cc0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slock_init':
(.text+0x2bf0): multiple definition of `me_slock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2e10): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_add_device_tail':
(.text+0x22e0): multiple definition of `me_dlist_add_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x22e0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_del_subdevice_tail':
(.text+0x2ad0): multiple definition of `me_slist_del_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2cf0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_get_number_devices':
(.text+0x22d0): multiple definition of `me_dlist_get_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22d0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slock_enter':
(.text+0x2b20): multiple definition of `me_slock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2d40): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_query_number_devices':
(.text+0x22c0): multiple definition of `me_dlist_query_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22c0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlist_del_device_tail':
(.text+0x23b0): multiple definition of `me_dlist_del_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x23b0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_subdevice_init':
(.text+0x27c0): multiple definition of `me_subdevice_init'
drivers/staging/meilhaus/me1000.o:(.text+0x29e0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_get_number_subdevices':
(.text+0x2930): multiple definition of `me_slist_get_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b50): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_device_deinit':
(.text+0xe0): multiple definition of `me_device_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0xe0): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlock_exit':
(.text+0x2430): multiple definition of `me_dlock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2430): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_device_pci_init':
(.text+0x130): multiple definition of `me_device_pci_init'
drivers/staging/meilhaus/me1000.o:(.text+0x130): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slist_get_subdevice_by_type':
(.text+0x29e0): multiple definition of `me_slist_get_subdevice_by_type'
drivers/staging/meilhaus/me1000.o:(.text+0x2c00): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_dlock_init':
(.text+0x2450): multiple definition of `me_dlock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2450): first defined here
drivers/staging/meilhaus/me4600.o: In function `me_slock_exit':
(.text+0x2b50): multiple definition of `me_slock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2d70): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlock_lock':
(.text+0x2470): multiple definition of `me_dlock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2470): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_deinit':
(.text+0x2320): multiple definition of `me_dlist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2320): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_get_device':
(.text+0x2380): multiple definition of `me_dlist_get_device'
drivers/staging/meilhaus/me1000.o:(.text+0x2380): first defined here
drivers/staging/meilhaus/me6000.o: In function `cleanup_module':
(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_add_subdevice_tail':
(.text+0x2940): multiple definition of `me_slist_add_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2b60): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_deinit':
(.text+0x2980): multiple definition of `me_slist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2ba0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlock_enter':
(.text+0x2400): multiple definition of `me_dlock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2400): first defined here
drivers/staging/meilhaus/me6000.o: In function `ao_stop_immediately':
(.text+0x39f0): multiple definition of `ao_stop_immediately'
drivers/staging/meilhaus/me4600.o:(.text+0x9290): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slock_deinit':
(.text+0x2be0): multiple definition of `me_slock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2e00): first defined here
drivers/staging/meilhaus/me6000.o: In function `ao_write_data_wraparound':
(.text+0x34e0): multiple definition of `ao_write_data_wraparound'
drivers/staging/meilhaus/me4600.o:(.text+0x8d80): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slock_lock':
(.text+0x2b60): multiple definition of `me_slock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2d80): first defined here
drivers/staging/meilhaus/me6000.o: In function `init_module':
(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/me6000.o: In function `ao_get_data_from_user':
(.text+0x3750): multiple definition of `ao_get_data_from_user'
drivers/staging/meilhaus/me4600.o:(.text+0x8ff0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_query_number_subdevices':
(.text+0x2920): multiple definition of `me_slist_query_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b40): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_init':
(.text+0x2960): multiple definition of `me_slist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2b80): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlock_deinit':
(.text+0x2440): multiple definition of `me_dlock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2440): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_xilinx_download':
(.text+0x2c10): multiple definition of `me_xilinx_download'
drivers/staging/meilhaus/me4600.o:(.text+0x2c10): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_subdevice_deinit':
(.text+0x27b0): multiple definition of `me_subdevice_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x29d0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_init':
(.text+0x2300): multiple definition of `me_dlist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2300): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_get_subdevice':
(.text+0x2aa0): multiple definition of `me_slist_get_subdevice'
drivers/staging/meilhaus/me1000.o:(.text+0x2cc0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slock_init':
(.text+0x2bf0): multiple definition of `me_slock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2e10): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_add_device_tail':
(.text+0x22e0): multiple definition of `me_dlist_add_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x22e0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_del_subdevice_tail':
(.text+0x2ad0): multiple definition of `me_slist_del_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2cf0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_get_number_devices':
(.text+0x22d0): multiple definition of `me_dlist_get_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22d0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slock_enter':
(.text+0x2b20): multiple definition of `me_slock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2d40): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_query_number_devices':
(.text+0x22c0): multiple definition of `me_dlist_query_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22c0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlist_del_device_tail':
(.text+0x23b0): multiple definition of `me_dlist_del_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x23b0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_subdevice_init':
(.text+0x27c0): multiple definition of `me_subdevice_init'
drivers/staging/meilhaus/me1000.o:(.text+0x29e0): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_get_number_subdevices':
(.text+0x2930): multiple definition of `me_slist_get_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b50): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_device_deinit':
(.text+0xe0): multiple definition of `me_device_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0xe0): first defined here
drivers/staging/meilhaus/me6000.o: In function `ao_write_data_pooling':
(.text+0x36a0): multiple definition of `ao_write_data_pooling'
drivers/staging/meilhaus/me4600.o:(.text+0x8f40): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlock_exit':
(.text+0x2430): multiple definition of `me_dlock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2430): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_device_pci_init':
(.text+0x130): multiple definition of `me_device_pci_init'
drivers/staging/meilhaus/me1000.o:(.text+0x130): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slist_get_subdevice_by_type':
(.text+0x29e0): multiple definition of `me_slist_get_subdevice_by_type'
drivers/staging/meilhaus/me1000.o:(.text+0x2c00): first defined here
drivers/staging/meilhaus/me6000.o: In function `ao_write_data':
(.text+0x35c0): multiple definition of `ao_write_data'
drivers/staging/meilhaus/me4600.o:(.text+0x8e60): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_dlock_init':
(.text+0x2450): multiple definition of `me_dlock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2450): first defined here
drivers/staging/meilhaus/me6000.o: In function `me_slock_exit':
(.text+0x2b50): multiple definition of `me_slock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2d70): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlock_lock':
(.text+0x2470): multiple definition of `me_dlock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2470): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_deinit':
(.text+0x2320): multiple definition of `me_dlist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2320): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_get_device':
(.text+0x2380): multiple definition of `me_dlist_get_device'
drivers/staging/meilhaus/me1000.o:(.text+0x2380): first defined here
drivers/staging/meilhaus/me8100.o: In function `cleanup_module':
(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_add_subdevice_tail':
(.text+0x2940): multiple definition of `me_slist_add_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2b60): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_deinit':
(.text+0x2980): multiple definition of `me_slist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2ba0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlock_enter':
(.text+0x2400): multiple definition of `me_dlock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2400): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slock_deinit':
(.text+0x2be0): multiple definition of `me_slock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2e00): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slock_lock':
(.text+0x2b60): multiple definition of `me_slock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2d80): first defined here
drivers/staging/meilhaus/me8100.o: In function `init_module':
(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_query_number_subdevices':
(.text+0x2920): multiple definition of `me_slist_query_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b40): first defined here
drivers/staging/meilhaus/me8100.o
: In function `me_slist_init':
(.text+0x2960): multiple definition of `me_slist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2b80): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlock_deinit':
(.text+0x2440): multiple definition of `me_dlock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2440): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_subdevice_deinit':
(.text+0x27b0): multiple definition of `me_subdevice_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x29d0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_init':
(.text+0x2300): multiple definition of `me_dlist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2300): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_get_subdevice':
(.text+0x2aa0): multiple definition of `me_slist_get_subdevice'
drivers/staging/meilhaus/me1000.o:(.text+0x2cc0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slock_init':
(.text+0x2bf0): multiple definition of `me_slock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2e10): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_add_device_tail':
(.text+0x22e0): multiple definition of `me_dlist_add_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x22e0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_del_subdevice_tail':
(.text+0x2ad0): multiple definition of `me_slist_del_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2cf0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_get_number_devices':
(.text+0x22d0): multiple definition of `me_dlist_get_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22d0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slock_enter':
(.text+0x2b20): multiple definition of `me_slock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2d40): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_query_number_devices':
(.text+0x22c0): multiple definition of `me_dlist_query_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22c0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlist_del_device_tail':
(.text+0x23b0): multiple definition of `me_dlist_del_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x23b0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_subdevice_init':
(.text+0x27c0): multiple definition of `me_subdevice_init'
drivers/staging/meilhaus/me1000.o:(.text+0x29e0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_get_number_subdevices':
(.text+0x2930): multiple definition of `me_slist_get_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b50): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_device_deinit':
(.text+0xe0): multiple definition of `me_device_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0xe0): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlock_exit':
(.text+0x2430): multiple definition of `me_dlock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2430): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_device_pci_init':
(.text+0x130): multiple definition of `me_device_pci_init'
drivers/staging/meilhaus/me1000.o:(.text+0x130): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slist_get_subdevice_by_type':
(.text+0x29e0): multiple definition of `me_slist_get_subdevice_by_type'
drivers/staging/meilhaus/me1000.o:(.text+0x2c00): first defined here
drivers/staging/meilhaus/me8100.o: In function `me8254_constructor':
(.text+0x2c80): multiple definition of `me8254_constructor'
drivers/staging/meilhaus/me4600.o:(.text+0x4070): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_dlock_init':
(.text+0x2450): multiple definition of `me_dlock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2450): first defined here
drivers/staging/meilhaus/me8100.o: In function `me_slock_exit':
(.text+0x2b50): multiple definition of `me_slock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2d70): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlock_lock':
(.text+0x2470): multiple definition of `me_dlock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2470): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_deinit':
(.text+0x2320): multiple definition of `me_dlist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2320): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_get_device':
(.text+0x2380): multiple definition of `me_dlist_get_device'
drivers/staging/meilhaus/me1000.o:(.text+0x2380): first defined here
drivers/staging/meilhaus/me8200.o: In function `cleanup_module':
(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_add_subdevice_tail':
(.text+0x2940): multiple definition of `me_slist_add_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2b60): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_deinit':
(.text+0x2980): multiple definition of `me_slist_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2ba0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlock_enter':
(.text+0x2400): multiple definition of `me_dlock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2400): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slock_deinit':
(.text+0x2be0): multiple definition of `me_slock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2e00): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slock_lock':
(.text+0x2b60): multiple definition of `me_slock_lock'
drivers/staging/meilhaus/me1000.o:(.text+0x2d80): first defined here
drivers/staging/meilhaus/me8200.o: In function `init_module':
(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_query_number_subdevices':
(.text+0x2920): multiple definition of `me_slist_query_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b40): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_init':
(.text+0x2960): multiple definition of `me_slist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2b80): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlock_deinit':
(.text+0x2440): multiple definition of `me_dlock_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x2440): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_subdevice_deinit':
(.text+0x27b0): multiple definition of `me_subdevice_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0x29d0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_init':
(.text+0x2300): multiple definition of `me_dlist_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2300): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_get_subdevice':
(.text+0x2aa0): multiple definition of `me_slist_get_subdevice'
drivers/staging/meilhaus/me1000.o:(.text+0x2cc0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slock_init':
(.text+0x2bf0): multiple definition of `me_slock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2e10): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_add_device_tail':
(.text+0x22e0): multiple definition of `me_dlist_add_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x22e0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_del_subdevice_tail':
(.text+0x2ad0): multiple definition of `me_slist_del_subdevice_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x2cf0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_get_number_devices':
(.text+0x22d0): multiple definition of `me_dlist_get_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22d0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slock_enter':
(.text+0x2b20): multiple definition of `me_slock_enter'
drivers/staging/meilhaus/me1000.o:(.text+0x2d40): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_query_number_devices':
(.text+0x22c0): multiple definition of `me_dlist_query_number_devices'
drivers/staging/meilhaus/me1000.o:(.text+0x22c0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlist_del_device_tail':
(.text+0x23b0): multiple definition of `me_dlist_del_device_tail'
drivers/staging/meilhaus/me1000.o:(.text+0x23b0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_subdevice_init':
(.text+0x27c0): multiple definition of `me_subdevice_init'
drivers/staging/meilhaus/me1000.o:(.text+0x29e0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_get_number_subdevices':
(.text+0x2930): multiple definition of `me_slist_get_number_subdevices'
drivers/staging/meilhaus/me1000.o:(.text+0x2b50): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_device_deinit':
(.text+0xe0): multiple definition of `me_device_deinit'
drivers/staging/meilhaus/me1000.o:(.text+0xe0): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlock_exit':
(.text+0x2430): multiple definition of `me_dlock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2430): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_device_pci_init':
(.text+0x130): multiple definition of `me_device_pci_init'
drivers/staging/meilhaus/me1000.o:(.text+0x130): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slist_get_subdevice_by_type':
(.text+0x29e0): multiple definition of `me_slist_get_subdevice_by_type'
drivers/staging/meilhaus/me1000.o:(.text+0x2c00): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_dlock_init':
(.text+0x2450): multiple definition of `me_dlock_init'
drivers/staging/meilhaus/me1000.o:(.text+0x2450): first defined here
drivers/staging/meilhaus/me8200.o: In function `me_slock_exit':
(.text+0x2b50): multiple definition of `me_slock_exit'
drivers/staging/meilhaus/me1000.o:(.text+0x2d70): first defined here
drivers/staging/meilhaus/medummy.o: In function `init_module':
medummy.c:(.init.text+0x0): multiple definition of `init_module'
drivers/staging/meilhaus/memain.o:memain.c:(.text+0x530): first defined here
drivers/staging/meilhaus/medummy.o: In function `cleanup_module':
medummy.c:(.exit.text+0x0): multiple definition of `cleanup_module'
drivers/staging/meilhaus/memain.o:memain.c:(.exit.text+0x0): first defined here
make[4]: *** [drivers/staging/meilhaus/built-in.o] Error 1
make[3]: *** [drivers/staging/meilhaus] Error 2
---
~Randy
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
drivers/staging/android/binder.c: In function 'binder_insert_free_buffer':
drivers/staging/android/binder.c:497: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c: In function 'binder_alloc_buf':
drivers/staging/android/binder.c:681: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:681: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c:690: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:711: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:720: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:720: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
drivers/staging/android/binder.c:748: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:757: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:757: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c: In function 'binder_free_buf':
drivers/staging/android/binder.c:831: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c:831: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
drivers/staging/android/binder.c:844: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:844: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c: In function 'binder_transaction':
drivers/staging/android/binder.c:1390: warning: format '%d' expects type 'int', but argument 9 has type 'size_t'
drivers/staging/android/binder.c:1390: warning: format '%d' expects type 'int', but argument 10 has type 'size_t'
drivers/staging/android/binder.c:1397: warning: format '%d' expects type 'int', but argument 9 has type 'size_t'
drivers/staging/android/binder.c:1397: warning: format '%d' expects type 'int', but argument 10 has type 'size_t'
drivers/staging/android/binder.c:1404: error: 'struct task_struct' has no member named 'euid'
drivers/staging/android/binder.c:1441: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c:1620: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
drivers/staging/android/binder.c:1620: warning: format '%d' expects type 'int', but argument 6 has type 'size_t'
drivers/staging/android/binder.c: In function 'binder_transaction_buffer_release':
drivers/staging/android/binder.c:1645: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c:1645: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
drivers/staging/android/binder.c:1658: warning: format '%d' expects type 'int', but argument 3 has type 'size_t'
drivers/staging/android/binder.c:1658: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c: In function 'binder_thread_read':
drivers/staging/android/binder.c:2359: warning: format '%d' expects type 'int', but argument 9 has type 'size_t'
drivers/staging/android/binder.c:2359: warning: format '%d' expects type 'int', but argument 10 has type 'size_t'
drivers/staging/android/binder.c:2593: error: 'struct task_struct' has no member named 'euid'
drivers/staging/android/binder.c:2596: error: 'struct task_struct' has no member named 'euid'
drivers/staging/android/binder.c:2602: error: 'struct task_struct' has no member named 'euid'
drivers/staging/android/binder.c: In function 'print_binder_transaction':
drivers/staging/android/binder.c:2934: warning: format '%d' expects type 'int', but argument 4 has type 'size_t'
drivers/staging/android/binder.c:2934: warning: format '%d' expects type 'int', but argument 5 has type 'size_t'
drivers/staging/android/binder.c: In function 'print_binder_buffer':
drivers/staging/android/binder.c:2943: warning: format '%d' expects type 'int', but argument 7 has type 'size_t'
drivers/staging/android/binder.c:2943: warning: format '%d' expects type 'int', but argument 8 has type 'size_t'
drivers/staging/android/binder.c: In function 'print_binder_proc_stats':
drivers/staging/android/binder.c:3212: warning: format '%d' expects type 'int', but argument 8 has type 'size_t'
make[4]: *** [drivers/staging/android/binder.o] Error 1
make[3]: *** [drivers/staging/android] Error 2
make[2]: *** [drivers/staging] Error 2
---
~Randy
On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> Hi all,
>
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
>
> Changes since 20090105:
>
> New tree:
> squashfs
>
> Undropped tree:
> usb
> staging
drivers/staging/android/timed_gpio.c:21:27: error: asm/arch/gpio.h: No such file or directory
drivers/staging/android/timed_gpio.c: In function 'gpio_timer_func':
drivers/staging/android/timed_gpio.c:41: error: implicit declaration of function 'gpio_direction_output'
drivers/staging/android/timed_gpio.c: In function 'gpio_enable_show':
drivers/staging/android/timed_gpio.c:52: error: 'ktime_t' has no member named 'tv'
drivers/staging/android/timed_gpio.c:52: error: 'ktime_t' has no member named 'tv'
make[4]: *** [drivers/staging/android/timed_gpio.o] Error 1
make[3]: *** [drivers/staging/android] Error 2
make[2]: *** [drivers/staging] Error 2
---
~Randy
On Tue, Jan 06, 2009 at 04:39:31PM -0800, Randy Dunlap wrote:
> On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
> >
> > Changes since 20090105:
> >
> > New tree:
> > squashfs
> >
> > Undropped tree:
> > usb
> > staging
>
>
> drivers/staging/android/timed_gpio.c:21:27: error: asm/arch/gpio.h: No such file or directory
Crap, this is an ARM specific thing :(
I'll fix this up after dinner...
thanks,
greg k-h
On Tuesday 06 January 2009, Iñaky Pérez-González wrote:
> On Tuesday 06 January 2009, Randy Dunlap wrote:
> > On Tue, 6 Jan 2009 18:23:11 +1100 Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > This tree will not build a powerpc ppc4xx_defconfig due to a kvm
> > > problem.
> > >
> > > Changes since 20090105:
> >
> > wimax build fails when CONFIG_INPUT=n:
>
> Ops -- my fault -- working on a fix.
>
> > Also, this warning needs to be fixed:
> >
> > linux-next-20090106/net/wimax/id-table.c:133: warning: ISO C90 forbids
> > mixed declarations and code
>
> Will fix too.
I just submitted a patchset to gregkh that fixes these issues and just
realized I didn't CC you guys:
http://linuxwimax.org/pipermail/wimax/2009-January/000397.html
My apologies for missing out,
--
Inaky
This commit was just merged:
Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=60f26520e7bd4479dbebf77317c45fc2255ba2e8
Commit: 60f26520e7bd4479dbebf77317c45fc2255ba2e8
Parent: d81408304b06a71c28417445202af9cd6673168d
Author: Alexey Korolev <[email protected]>
AuthorDate: Tue Dec 16 18:24:14 2008 +0000
Committer: David Woodhouse <[email protected]>
CommitDate: Mon Jan 5 13:58:47 2009 +0100
[MTD] LPDDR Makefile and KConfig
but the patch below is missing/still needed.
Alexey Korolev wrote:
> Hi Randy,
>
>> # CONFIG_MTD_LPDDR is not set
>> CONFIG_MTD_QINFO_PROBE=y
>>
>> There appears to be too little control/coordination between those
>> two kconfig symbols. Surely one of them (MTD_QINFO_PROBE) should
>> depend on the other (MTD_LPDDR). And why even build 2 modules
>> when MTD_QINFO_PROBE is enabled? Why not combine the code into
>> one module?
> Thanks a lot for good finding. Here is a fix for the problem.
>
> About combining: it is assumed to have one QINFO probing module for several
> kinds of LPDDR command set drivers. If we combine two modules into
> one it would make further extension rather hard. So it is better to have
> two modules.
> To fix a problem I just added dependency in Kconfig file.
> This temporary fix which will work until we have just one cmdset module.
> In near future we will make a fix which parse command set types
> and select proper driver according to device type.
>
> Thanks,
> Alexey
>
> Signed-off-by: Alexey Korolev <[email protected]>
> ---
> diff --git a/drivers/mtd/lpddr/Kconfig b/drivers/mtd/lpddr/Kconfig
> index acd4ea9..5a401d8 100644
> --- a/drivers/mtd/lpddr/Kconfig
> +++ b/drivers/mtd/lpddr/Kconfig
> @@ -12,6 +12,7 @@ config MTD_LPDDR
> DDR memories, intended for battery-operated systems.
>
> config MTD_QINFO_PROBE
> + depends on MTD_LPDDR
> tristate "Detect flash chips by QINFO probe"
> help
> Device Information for LPDDR chips is offered through the Overlay
>
>
--
~Randy