linux-next: Tree for August 10
Subsystems (3)
Hi all,
As the merge window is open, please do not add 2.6.37 material to your linux-next included trees until after 2.6.36-rc1.
Changes since 20100809:
The block tree lost its build failure.
The mfd tree lost its build failure.
The trivial tree gained conflicts against the vfs tree and Linus's tree.
The catalin tree lost its conflicts.
----------------------------------------------------------------------------
I have created today's linux-next tree atgit://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/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 (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc and sparc64 defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 169 trees (counting Linus' and 22 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.
Signature · 229 lines
Cheers, Stephen Rothwell [email protected] $ git checkout master $ git reset --hard stable Merging origin/master Merging fixes/fixes 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/rc-fixes Merging quilt/driver-core.current Merging quilt/tty.current Merging quilt/usb.current Merging quilt/staging.current Merging cpufreq-current/fixes Merging input-current/for-linus Merging md-current/for-linus Merging audit-current/for-linus Merging crypto-current/master Merging ide-curent/master Merging dwmw2/master Merging gcl-current/merge Merging arm/devel CONFLICT (content): Merge conflict in arch/arm/Kconfig CONFLICT (content): Merge conflict in arch/arm/mm/Kconfig Merging davinci/davinci-next Merging i.MX/for-next Merging msm/for-next Merging omap/for-next Merging pxa/for-next Merging samsung/next-samsung Merging s5p/for-next Merging tegra/for-next CONFLICT (content): Merge conflict in arch/arm/Kconfig CONFLICT (content): Merge conflict in arch/arm/mm/Kconfig Merging avr32/avr32-arch Merging blackfin/for-linus Merging cris/for-next Merging ia64/test Merging m68k/for-next Merging m68knommu/for-next Merging microblaze/next Merging mips/mips-for-linux-next Merging parisc/next Merging powerpc/next Merging 4xx/next Merging 52xx-and-virtex/next Merging galak/next Merging s390/features Merging sh/master CONFLICT (content): Merge conflict in drivers/Makefile Merging genesis/master Merging sparc/master Merging tile/master Merging xtensa/master CONFLICT (content): Merge conflict in arch/xtensa/configs/iss_defconfig Merging ceph/for-next Applying: ceph: update for removal of request flag wrappers Merging cifs/master Merging configfs/linux-next Merging ecryptfs/next Merging ext3/for_next Merging ext4/next Merging fatfs/master Merging fuse/for-next Merging gfs2/master Merging jfs/next Merging logfs/master CONFLICT (content): Merge conflict in fs/logfs/logfs.h Merging nfs/linux-next Merging nfsd/nfsd-next Merging nilfs2/for-next Merging ocfs2/linux-next Merging omfs/for-next Merging squashfs/master Merging udf/for_next Merging v9fs/for-next Merging ubifs/linux-next Merging xfs/master Merging vfs/for-next CONFLICT (content): Merge conflict in fs/nilfs2/super.c CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_aops.c CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_super.c Applying: v9fs: fixup for inode_setattr being removed Applying: xfs: update tracing for clear_inode to evit_inode transition Applying: cifs: fix for clear_inode -> evict_inode API change Merging pci/linux-next Merging hid/for-next Merging quilt/i2c Merging bjdooks-i2c/next-i2c CONFLICT (content): Merge conflict in arch/arm/plat-omap/i2c.c CONFLICT (content): Merge conflict in drivers/i2c/busses/i2c-cpm.c CONFLICT (content): Merge conflict in drivers/i2c/busses/i2c-mpc.c Merging quilt/jdelvare-hwmon Merging quilt/kernel-doc CONFLICT (content): Merge conflict in Documentation/kernel-parameters.txt Merging v4l-dvb/master Merging kbuild/for-next Merging kconfig/for-next Merging ide/master Merging libata/NEXT Merging infiniband/for-next Merging acpi/test Merging idle-test/idle-test Merging ieee1394/for-next Merging ubi/linux-next Merging kvm/linux-next Merging dlm/next Merging swiotlb/master Merging swiotlb-xen/master CONFLICT (content): Merge conflict in drivers/xen/Kconfig CONFLICT (content): Merge conflict in drivers/xen/Makefile CONFLICT (content): Merge conflict in include/xen/xen-ops.h Merging ibft/master Merging scsi/master Merging async_tx/next CONFLICT (content): Merge conflict in arch/arm/mach-ux500/devices-db8500.c Merging net/master Merging wireless/master Merging mtd/master CONFLICT (content): Merge conflict in drivers/mtd/maps/Kconfig CONFLICT (delete/modify): drivers/mtd/maps/redwood.c deleted in mtd/master and modified in HEAD. Version HEAD of drivers/mtd/maps/redwood.c left in tree. $ git rm -f drivers/mtd/maps/redwood.c Merging crypto/master Merging sound/for-next Merging cpufreq/next Merging quilt/rr CONFLICT (content): Merge conflict in arch/um/drivers/hostaudio_kern.c CONFLICT (content): Merge conflict in kernel/module.c Applying: nfs: update for module_param_named API change Applying: AppArmor: update for module_param_named API change Merging input/next Merging lsm/for-next Merging block/for-next CONFLICT (content): Merge conflict in drivers/block/virtio_blk.c CONFLICT (content): Merge conflict in drivers/scsi/scsi_error.c Merging quilt/device-mapper CONFLICT (content): Merge conflict in drivers/md/dm.c Merging embedded/master Merging firmware/master Merging pcmcia/master Merging battery/master CONFLICT (content): Merge conflict in drivers/power/Kconfig CONFLICT (content): Merge conflict in drivers/power/Makefile 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 mfd/for-next Merging hdlc/hdlc-next Merging drm/drm-next Merging viafb/viafb-next Merging voltage/for-next Merging security-testing/next Merging lblnet/master Merging agp/agp-next Merging uwb/for-upstream Merging watchdog/master Merging bdev/master Merging dwmw2-iommu/master Merging cputime/cputime Merging osd/linux-next Merging jc_docs/docs-next Merging nommu/master Merging trivial/for-next CONFLICT (content): Merge conflict in arch/arm/mach-omap1/board-nokia770.c CONFLICT (content): Merge conflict in fs/exofs/inode.c Merging audit/for-next Merging quilt/aoe Merging suspend/linux-next Merging bluetooth/master Merging fsnotify/for-next CONFLICT (delete/modify): fs/notify/inotify/inotify.c deleted in fsnotify/for-next and modified in HEAD. Version HEAD of fs/notify/inotify/inotify.c left in tree. $ git rm -f fs/notify/inotify/inotify.c Merging irda/for-next CONFLICT (content): Merge conflict in drivers/net/irda/irda-usb.c Merging catalin/for-next Merging alacrity/linux-next Merging i7core_edac/linux_next CONFLICT (content): Merge conflict in MAINTAINERS Merging devicetree/next-devicetree Merging spi/next-spi CONFLICT (content): Merge conflict in drivers/spi/mpc512x_psc_spi.c Applying: spi: update for of_device to platform_device replacement Merging limits/writable_limits CONFLICT (content): Merge conflict in arch/x86/ia32/ia32entry.S CONFLICT (content): Merge conflict in arch/x86/include/asm/unistd_32.h CONFLICT (content): Merge conflict in arch/x86/include/asm/unistd_64.h CONFLICT (content): Merge conflict in arch/x86/kernel/syscall_table_32.S CONFLICT (content): Merge conflict in include/asm-generic/unistd.h Merging omap_dss2/for-next Merging xen/upstream/xen Merging tip/auto-latest Merging lost-spurious-irq/lost-spurious-irq CONFLICT (content): Merge conflict in drivers/ata/sata_fsl.c CONFLICT (content): Merge conflict in drivers/ata/sata_mv.c CONFLICT (content): Merge conflict in drivers/ata/sata_nv.c CONFLICT (content): Merge conflict in include/linux/libata.h Merging edac-amd/for-next Merging oprofile/for-next Merging percpu/for-next Merging workqueues/for-next Merging sfi/sfi-test Merging asm-generic/next Merging drivers-x86/linux-next Merging hwpoison/hwpoison CONFLICT (content): Merge conflict in mm/memory-failure.c Merging sysctl/master Merging bkl-core/bkl/core Merging bkl-procfs/bkl/procfs Merging bkl-ioctl/bkl/ioctl Merging quilt/driver-core Merging quilt/tty CONFLICT (content): Merge conflict in drivers/char/vt.c CONFLICT (content): Merge conflict in include/linux/serial_core.h Merging quilt/usb Merging staging-next/staging-next Merging slabh/slabh Merging scsi-post-merge/merge-base:master $ git checkout scsi-post-merge/master
Quoted 4 lines · On Tue, 10 Aug 2010 13:56:01 +1000 Stephen Rothwell <[email protected]>…
Hi all,
As the merge window is open, please do not add 2.6.37 material to your linux-next included trees until after 2.6.36-rc1.
Breaks on x86-32 with
ERROR: "st_get_plat_device" [drivers/staging/ti-st/st_drv.ko] undefined!
ERROR: "__get_user_X" [drivers/acpi/apei/erst-dbg.ko] undefined!
WARNING: modpost: Found 17 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
Alan
PATCH 1/1 mfd: tps6586x depends on GPIOLIB
In reply to Stephen RothwellFrom: Randy Dunlap <[email protected]>
tps6586x uses gpio interfaces, so it should depend on GPIOLIB.
Fixes these build errors:
drivers/mfd/tps6586x.c:41: error: field 'gpio' has incomplete type drivers/mfd/tps6586x.c:195: warning: type defaults to 'int' in declaration of '__mptr' drivers/mfd/tps6586x.c:195: warning: initialization from incompatible pointer type drivers/mfd/tps6586x.c:210: warning: type defaults to 'int' in declaration of '__mptr' drivers/mfd/tps6586x.c:210: warning: initialization from incompatible pointer type drivers/mfd/tps6586x.c:219: warning: type defaults to 'int' in declaration of '__mptr' drivers/mfd/tps6586x.c:219: warning: initialization from incompatible pointer type drivers/mfd/tps6586x.c:249: error: implicit declaration of function 'gpiochip_add'
--- drivers/mfd/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/mfd/Kconfig +1 -1
@@ -543,7 +543,7 @@ config MFD_JZ4740_ADC config MFD_TPS6586X tristate "TPS6586x Power Management chips" - depends on I2C + depends on I2C && GPIOLIB select MFD_CORE help If you say yes here you get support for the TPS6586X series of
Re: [PATCH -next] mfd: tps6586x depends on GPIOLIB
Quoted 3 lines · Randy Dunlap
From: Randy Dunlap <[email protected]>
tps6586x uses gpio interfaces, so it should depend on GPIOLIB.
Thanks Randy, I merged this one into the yet to be pulled tps6586x driver.
Cheers,
Samuel.
Quoted 28 lines
Fixes these build errors:
drivers/mfd/tps6586x.c:41: error: field 'gpio' has incomplete typedrivers/mfd/tps6586x.c:195: warning: type defaults to 'int' in declaration of '__mptr'drivers/mfd/tps6586x.c:195: warning: initialization from incompatible pointer typedrivers/mfd/tps6586x.c:210: warning: type defaults to 'int' in declaration of '__mptr'drivers/mfd/tps6586x.c:210: warning: initialization from incompatible pointer typedrivers/mfd/tps6586x.c:219: warning: type defaults to 'int' in declaration of '__mptr'drivers/mfd/tps6586x.c:219: warning: initialization from incompatible pointer typedrivers/mfd/tps6586x.c:249: error: implicit declaration of function 'gpiochip_add'Signed-off-by Randy Dunlap <[email protected]>Cc Samuel Ortiz <[email protected]>--- drivers/mfd/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/mfd/Kconfig +1
-1@@ -543,7 +543,7 @@ config MFD_JZ4740_ADC config MFD_TPS6586X tristate "TPS6586x Power Management chips" - depends on I2C + depends on I2C && GPIOLIB select MFD_CORE help If you say yes here you get support for the TPS6586X series of
Signature · 2 lines
Intel Open Source Technology Centre http://oss.intel.com/
Re: linux-next: Tree for August 10 (acpi/apei)
In reply to Stephen RothwellQuoted 6 lines · On Tue, 10 Aug 2010 13:56:01 +1000 Stephen Rothwell wrote:
Hi all,
As the merge window is open, please do not add 2.6.37 material to your linux-next included trees until after 2.6.36-rc1.
Changes since 20100809:
on 32-bit i386:
drivers/acpi/apei/erst-dbg.c:106: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'ssize_t' erst-dbg.c:(.text+0xede6d): undefined reference to `__get_user_X'
For the __get_user_X() call, in erst-dbg.c::erst_dbg_ioctl():
case APEI_ERST_CLEAR_RECORD: rc = get_user(record_id, (u64 __user *)arg);
-> arch/x86/include/asm/uaccess.h:
#ifdef CONFIG_X86_32
#define __get_user_8(__ret_gu, __val_gu, ptr) \ __get_user_x(X, __ret_gu, __val_gu, ptr) #else #define __get_user_8(__ret_gu, __val_gu, ptr) \ __get_user_x(8, __ret_gu, __val_gu, ptr)
#endif
so is __get_user_8() not supported on X86_32?
or is this something else?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
Re: linux-next: Tree for August 10 (acpi/apei)
Quoted 28 lines · Randy Dunlap
Quoted 6 lines · On Tue, 10 Aug 2010 13:56:01 +1000 Stephen Rothwell wrote:
Hi all,
As the merge window is open, please do not add 2.6.37 material to your linux-next included trees until after 2.6.36-rc1.
Changes since 20100809:
on 32-bit i386:
drivers/acpi/apei/erst-dbg.c:106: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'ssize_t' erst-dbg.c:(.text+0xede6d): undefined reference to `__get_user_X'For the
__get_user_X()call, in erst-dbg.c::erst_dbg_ioctl():case APEI_ERST_CLEAR_RECORD: rc = get_user(record_id, (u64 __user *)arg);->
arch/x86/include/asm/uaccess.h:#ifdef
CONFIG_X86_32#define __get_user_8(__ret_gu, __val_gu, ptr) \ __get_user_x(X, __ret_gu, __val_gu, ptr) #else #define __get_user_8(__ret_gu, __val_gu, ptr) \ __get_user_x(8, __ret_gu, __val_gu, ptr)
Quoted 5 lines
#endif
so is
__get_user_8()not supported onX86_32?
or is this something else?
Will fix that via replacing get_user with copy_from_user for u64.
Best Regards,
Huang Ying