Hi all,
Changes since 20100708:
The infiniband tree gained a build failure so I used the version from
next-20100708.
The wireless tree gained a conflict against the net tree.
The block tree gained a build failure for which I applied a patch.
The tty tree gained a conflict against the genesis tree.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://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 164 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.
--
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
Merging davinci/davinci-next
Merging i.MX/for-next
Merging msm/for-next
Merging omap/for-next
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-3430sdp.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-3630sdp.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-am3517evm.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-cm-t35.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-devkit8000.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-igep0020.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-ldp.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-omap3beagle.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-omap3evm.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-omap3pandora.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-omap3touchbook.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-overo.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-zoom2.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-zoom3.c
Merging pxa/for-next
Merging samsung/next-samsung
Merging s5p/for-next
Merging tegra/for-next
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
CONFLICT (content): Merge conflict in drivers/serial/mpc52xx_uart.c
Merging galak/next
Merging s390/features
Merging sh/master
Merging genesis/master
Merging sparc/master
Merging tile/master
Merging xtensa/master
Merging ceph/for-next
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 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_super.c
Applying: v9fs: fixup for inode_setattr being removed
Applying: xfs: update tracing for clear_inode to evit_inode transition
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
Merging v4l-dvb/master
CONFLICT (content): Merge conflict in drivers/staging/tm6000/tm6000-alsa.c
Merging kbuild/for-next
Merging kconfig/for-next
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
$ git reset --hard HEAD^
Merging refs/next/20100708/infiniband
Merging acpi/test
Merging idle-test/idle-test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/linux-next
Merging dlm/next
Merging ibft/master
Merging swiotlb/master
Merging scsi/master
Merging async_tx/next
Merging net/master
Merging wireless/master
CONFLICT (content): Merge conflict in drivers/net/wireless/wl12xx/wl1271_cmd.h
Merging mtd/master
Merging crypto/master
Merging sound/for-next
CONFLICT (content): Merge conflict in Documentation/kernel-parameters.txt
Merging cpufreq/next
Merging quilt/rr
CONFLICT (content): Merge conflict in kernel/module.c
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 fs/fs-writeback.c
CONFLICT (content): Merge conflict in include/linux/backing-dev.h
CONFLICT (content): Merge conflict in mm/backing-dev.c
Merging quilt/device-mapper
CONFLICT (content): Merge conflict in drivers/md/dm.c
Applying: device-mapper: fix for bio API change
Merging embedded/master
Merging firmware/master
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 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 (delete/modify): drivers/media/video/ov511.c deleted in HEAD and modified in trivial/for-next. Version trivial/for-next of drivers/media/video/ov511.c left in tree.
$ git rm -f drivers/media/video/ov511.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
Applying: fsnotify: update gfp/slab.h includes
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
Merging devicetree/next-devicetree
Merging spi/next-spi
Merging omap_dss2/for-next
Merging tip/auto-latest
CONFLICT (content): Merge conflict in Makefile
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 include/linux/serial_core.h
Merging quilt/usb
CONFLICT (content): Merge conflict in drivers/media/video/uvc/uvcvideo.h
CONFLICT (content): Merge conflict in include/linux/usb/video.h
Merging staging-next/staging-next
CONFLICT (content): Merge conflict in drivers/staging/batman-adv/bat_sysfs.c
CONFLICT (delete/modify): drivers/staging/batman-adv/device.c deleted in staging-next/staging-next and modified in HEAD. Version HEAD of drivers/staging/batman-adv/device.c left in tree.
CONFLICT (delete/modify): drivers/staging/cx25821/cx25821-audups11.c deleted in HEAD and modified in staging-next/staging-next. Version staging-next/staging-next of drivers/staging/cx25821/cx25821-audups11.c left in tree.
$ git rm -f drivers/staging/cx25821/cx25821-audups11.c
$ git rm -f drivers/staging/batman-adv/device.c
Merging slabh/slabh
Merging scsi-post-merge/master
Applying: block: fix for block tracing build error
With today's next(20100709) qeth interface fails to initialize
with following Badness message:
sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
------------ cut here ------------
Badness at fs/sysfs/symlink.c:82
Modules linked in: qeth_l3 ipv6 qeth qdio vmur ccwgroup scsi_dh_alua scsi_dh_rda
c scsi_dh_hp_sw scsi_dh_emc dm_zero ext3 mbcache multipath jbd dm_snapshot dm_mi
rror dm_region_hash dm_log dm_round_robin dm_multipath dm_mod scsi_dh sd_mod scs
i_mod crc_t10dif dasd_fba_mod dasd_eckd_mod dasd_mod
CPU: 0 Tainted: G W 2.6.35-rc4-autotest-next-20100709-5-default #1
Process udevd (pid: 587, task: 00000000fcdc0038, ksp: 00000000faa4f9a8)
Krnl PSW : 0704000180000000 00000000002ac5b0 (sysfs_do_create_link+0x120/0x268)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:0 PM:0 EA:3
Krnl GPRS: 0000000000010000 0000000000719408 0000000000000043 00000000ffffffff
000000000045bf5a 0000000000000000 00000000fa96b640 0000000000000001
0000000000000001 00000000faa4fbb0 00000000fca76500 00000000fb139a50
0000000000000000 000000000048be60 00000000002ac5ac 00000000faa4fb10
Krnl Code: 00000000002ac5a0: c020001545ad larl %r2,5550fa
00000000002ac5a6: c0e5000d7cb1 brasl %r14,45bf08
00000000002ac5ac: a7f40001 brc 15,2ac5ae
>00000000002ac5b0: b9040029 lgr %r2,%r9
00000000002ac5b4: a7c8ffea lhi %r12,-22
00000000002ac5b8: c0e5fffffbf8 brasl %r14,2abda8
00000000002ac5c2: 5830b000 l %r3,0(%r11)
Call Trace:
(<00000000002ac5ac> sysfs_do_create_link+0x11c/0x268)
<0000000000358f62> device_add+0x6c2/0x734
<00000000003cffa8> netdev_register_kobject+0x88/0x188
<00000000003be7aa> register_netdevice+0x236/0x450
<00000000003bea1e> register_netdev+0x5a/0x74
<000003c00633a5b8> __qeth_l3_set_online+0x9d8/0x1518 qeth_l3
<000003c004cb4ada> ccwgroup_online_store+0x1e6/0x230 ccwgroup
<00000000002a9e10> sysfs_write_file+0xec/0x19c
<00000000002301d0> vfs_write+0xac/0x184
<000000000023039e> SyS_write+0x52/0xa8
<00000000001195ee> sysc_noemu+0x10/0x16
<0000020000151444> 0x20000151444
Last Breaking-Event-Address:
<00000000002ac5ac> sysfs_do_create_link+0x11c/0x268
Yesterday's next was good.
Last commit that changed symlink.c was
commit d7866652cda316006089fa42b931627992c08010
sysfs: Don't allow the creation of symlinks we can't remove
This commit added the above WARN() message. I haven't tried to revert
this commit to check if that helps with qeth initialization.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
Sachin Sant <[email protected]> writes:
> With today's next(20100709) qeth interface fails to initialize
> with following Badness message:
> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
Is this with CONFIG_SYSFS_DEPRECATED set?
I think I may have made my warning check a little extra strict.
Eric
Eric W. Biederman wrote:
>> With today's next(20100709) qeth interface fails to initialize
>> with following Badness message:
>>
>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
>>
>
> Is this with CONFIG_SYSFS_DEPRECATED set?
>
> I think I may have made my warning check a little extra strict.
>
Yes.
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
Sachin Sant <[email protected]> writes:
> Eric W. Biederman wrote:
>>> With today's next(20100709) qeth interface fails to initialize
>>> with following Badness message:
>>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
>>>
>>
>> Is this with CONFIG_SYSFS_DEPRECATED set?
>>
>> I think I may have made my warning check a little extra strict.
>>
> Yes.
>
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
Ugh. It looks like the warning is correct and I have a regression
in 2.6.35 that was overlooked because I did not closely test
CONIFG_SYSFS_DEPRECATED. I will see if I can cook up a proper
patch shortly.
Eric
On Fri, Jul 09, 2010 at 03:57:00PM +0530, Sachin Sant wrote:
> Eric W. Biederman wrote:
>>> With today's next(20100709) qeth interface fails to initialize
>>> with following Badness message:
>>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
>>>
>>
>> Is this with CONFIG_SYSFS_DEPRECATED set?
>>
>> I think I may have made my warning check a little extra strict.
>>
> Yes.
>
> CONFIG_SYSFS_DEPRECATED=y
> CONFIG_SYSFS_DEPRECATED_V2=y
Why do you have those options enabled? Does your userspace really
require them? I want to remove those options soon, and it would be good
to find out what is still relying on them.
If you disable those options, does it then work?
thanks,
greg k-h
On Fri, 9 Jul 2010 07:28:18 -0700
Greg KH <[email protected]> wrote:
> On Fri, Jul 09, 2010 at 03:57:00PM +0530, Sachin Sant wrote:
> > Eric W. Biederman wrote:
> >>> With today's next(20100709) qeth interface fails to initialize
> >>> with following Badness message:
> >>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
> >>>
> >>
> >> Is this with CONFIG_SYSFS_DEPRECATED set?
> >>
> >> I think I may have made my warning check a little extra strict.
> >>
> > Yes.
> >
> > CONFIG_SYSFS_DEPRECATED=y
> > CONFIG_SYSFS_DEPRECATED_V2=y
>
> Why do you have those options enabled? Does your userspace really
> require them? I want to remove those options soon, and it would be good
> to find out what is still relying on them.
>
> If you disable those options, does it then work?
The default configuration for s390 does not have the options enabled and
with a recent userspace everything works just fine. From my point of view
the two options can be removed.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
Greg KH wrote:
> On Fri, Jul 09, 2010 at 03:57:00PM +0530, Sachin Sant wrote:
>
>> Eric W. Biederman wrote:
>>
>>>> With today's next(20100709) qeth interface fails to initialize
>>>> with following Badness message:
>>>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
>>>>
>>>>
>>> Is this with CONFIG_SYSFS_DEPRECATED set?
>>>
>>> I think I may have made my warning check a little extra strict.
>>>
>>>
>> Yes.
>>
>> CONFIG_SYSFS_DEPRECATED=y
>> CONFIG_SYSFS_DEPRECATED_V2=y
>>
>
> Why do you have those options enabled? Does your userspace really
> require them? I want to remove those options soon, and it would be good
> to find out what is still relying on them.
>
> If you disable those options, does it then work?
>
Not sure when and why i enabled these options.
Without them i don't see any problem (including the badness).
Thanks
-Sachin
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-s390" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
On Fri, Jul 09, 2010 at 05:33:26PM +0200, Martin Schwidefsky wrote:
> On Fri, 9 Jul 2010 07:28:18 -0700
> Greg KH <[email protected]> wrote:
>
> > On Fri, Jul 09, 2010 at 03:57:00PM +0530, Sachin Sant wrote:
> > > Eric W. Biederman wrote:
> > >>> With today's next(20100709) qeth interface fails to initialize
> > >>> with following Badness message:
> > >>> sysfs: symlink across ns_types 0.0.6000/net:eth0 -> net/eth0
> > >>>
> > >>
> > >> Is this with CONFIG_SYSFS_DEPRECATED set?
> > >>
> > >> I think I may have made my warning check a little extra strict.
> > >>
> > > Yes.
> > >
> > > CONFIG_SYSFS_DEPRECATED=y
> > > CONFIG_SYSFS_DEPRECATED_V2=y
> >
> > Why do you have those options enabled? Does your userspace really
> > require them? I want to remove those options soon, and it would be good
> > to find out what is still relying on them.
> >
> > If you disable those options, does it then work?
>
> The default configuration for s390 does not have the options enabled and
> with a recent userspace everything works just fine. From my point of view
> the two options can be removed.
Wonderful, thanks for letting me know.
Sachin, care to disable them in your image as well?
thanks,
greg k-h
On Fri, 9 Jul 2010 15:01:17 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100708:
>
> The infiniband tree gained a build failure so I used the version from
> next-20100708.
>
> The wireless tree gained a conflict against the net tree.
>
> The block tree gained a build failure for which I applied a patch.
>
> The tty tree gained a conflict against the genesis tree.
when CONFIG_GPIOLIB is not enabled:
drivers/serial/max3107.h:372: error: field 'chip' has incomplete type
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
On Fri, 9 Jul 2010 15:01:17 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100708:
>
> The infiniband tree gained a build failure so I used the version from
> next-20100708.
>
> The wireless tree gained a conflict against the net tree.
>
> The block tree gained a build failure for which I applied a patch.
>
> The tty tree gained a conflict against the genesis tree.
When both batman-adv and dt3155 are enabled as builtin (=y):
drivers/staging/dt3155/built-in.o: In function `cleanup_module':
(.text+0xc0): multiple definition of `cleanup_module'
drivers/staging/batman-adv/built-in.o:(.text+0x330): first defined here
drivers/staging/dt3155/built-in.o: In function `init_module':
(.text+0x1120): multiple definition of `init_module'
drivers/staging/batman-adv/built-in.o:(.text+0x400): first defined here
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
On Fri, 9 Jul 2010 15:01:17 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100708:
>
> The infiniband tree gained a build failure so I used the version from
> next-20100708.
>
> The wireless tree gained a conflict against the net tree.
>
> The block tree gained a build failure for which I applied a patch.
>
> The tty tree gained a conflict against the genesis tree.
Can't find this function in the linux-next source tree:
ERROR: "st_get_plat_device" [drivers/staging/ti-st/st_drv.ko] undefined!
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
On Sun, 11 Jul 2010 15:33:16 -0700 Randy Dunlap wrote:
> On Fri, 9 Jul 2010 15:01:17 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20100708:
> >
> > The infiniband tree gained a build failure so I used the version from
> > next-20100708.
> >
> > The wireless tree gained a conflict against the net tree.
> >
> > The block tree gained a build failure for which I applied a patch.
> >
> > The tty tree gained a conflict against the genesis tree.
>
>
> Can't find this function in the linux-next source tree:
>
> ERROR: "st_get_plat_device" [drivers/staging/ti-st/st_drv.ko] undefined!
Still seeing this error in linux-next 20100719.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
On Sun, 11 Jul 2010 15:27:23 -0700 Randy Dunlap wrote:
> On Fri, 9 Jul 2010 15:01:17 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20100708:
> >
> > The infiniband tree gained a build failure so I used the version from
> > next-20100708.
> >
> > The wireless tree gained a conflict against the net tree.
> >
> > The block tree gained a build failure for which I applied a patch.
> >
> > The tty tree gained a conflict against the genesis tree.
>
>
> when CONFIG_GPIOLIB is not enabled:
>
> drivers/serial/max3107.h:372: error: field 'chip' has incomplete type
This build still fails in linux-next 20100719.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
> > when CONFIG_GPIOLIB is not enabled:
> >
> > drivers/serial/max3107.h:372: error: field 'chip' has incomplete type
>
>
> This build still fails in linux-next 20100719.
I'll put next tonight and have a detailed look at this one.
Alan