* linux-next: Tree for March 11 @ 2009-03-11 11:59 Stephen Rothwell 2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap 2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap 0 siblings, 2 replies; 16+ messages in thread From: Stephen Rothwell @ 2009-03-11 11:59 UTC (permalink / raw) To: linux-next; +Cc: LKML [-- Attachment #1: Type: text/plain, Size: 10552 bytes --] Hi all, Changes since 20090310: The xfs tree still has a build failure and so is still the version from next-20090306. The net tee lost its 2 conficts. The input tree lost its build failure. The md tree lost its conflict and build failure, but gained another build failure, so I used the tree from next-20090306. The lblnet tree lost its conflict. The watchdog tree lost its 2 conflicts. The proc tree removed an struct element used by a new driver in the block tree so I have applied a merge fixup patch. ---------------------------------------------------------------------------- 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 (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES) 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 133 trees (counting Linus' and 18 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 sfr@canb.auug.org.au $ 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 Merging crypto-current/master Merging dwmw2/master Merging arm/devel CONFLICT (content): Merge conflict in arch/arm/mach-at91/gpio.c 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 CONFLICT (rename/modify): Merge conflict in arch/arm/plat-pxa/dma.c Merging s390/features Merging sh/master Merging sparc/master Merging x86/auto-x86-next CONFLICT (content): Merge conflict in arch/powerpc/include/asm/elf.h Merging xtensa/master Merging tip-core/auto-core-next CONFLICT (content): Merge conflict in lib/Kconfig.debug Merging cpus4096/auto-cpus4096-next Merging tracing/auto-tracing-next CONFLICT (content): Merge conflict in arch/x86/Kconfig CONFLICT (delete/modify): block/blktrace.c deleted in tracing/auto-tracing-next and modified in HEAD. Version HEAD of block/blktrace.c left in tree. CONFLICT (content): Merge conflict in kernel/irq/handle.c $ git rm -f block/blktrace.c Applying: tracing: blktrace merge fix Applying: trace: percpu fixup Merging genirq/auto-genirq-next CONFLICT (content): Merge conflict in kernel/irq/handle.c Merging safe-poison-pointers/auto-safe-poison-pointers-next Merging sched/auto-sched-next CONFLICT (content): Merge conflict in lib/Makefile Merging stackprotector/auto-stackprotector-next Merging timers/auto-timers-next Merging pci/linux-next CONFLICT (content): Merge conflict in drivers/pci/pcie/portdrv_pci.c Merging quilt/device-mapper Merging hid/for-next Merging quilt/i2c 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 quota/for_next Merging jfs/next Merging kbuild/master Merging quilt/ide Merging libata/NEXT Merging nfs/linux-next Merging xfs/master $ git reset --hard HEAD^ Merging xfs/master from next-20090306 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 Merging ocfs2/linux-next Merging ext4/next CONFLICT (content): Merge conflict in fs/ext4/inode.c Merging async_tx/next Merging udf/for_next Merging net/master Merging wireless/master Merging mtd/master Merging crypto/master Merging vfs/for-next Merging sound/for-next CONFLICT (content): Merge conflict in arch/arm/mach-shark/include/mach/io.h CONFLICT (content): Merge conflict in sound/soc/pxa/pxa2xx-i2s.c Merging cpufreq/next CONFLICT (content): Merge conflict in arch/x86/include/asm/timer.h Merging v9fs/for-next CONFLICT (content): Merge conflict in net/9p/protocol.c Merging quilt/rr CONFLICT (content): Merge conflict in arch/powerpc/kernel/irq.c CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/cpufreq/powernow-k8.c CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/cpufreq/speedstep-ich.c CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/cpufreq/speedstep-lib.c CONFLICT (delete/modify): arch/x86/mach-default/setup.c deleted in HEAD and modified in quilt/rr. Version quilt/rr of arch/x86/mach-default/setup.c left in tree. CONFLICT (delete/modify): arch/x86/mach-voyager/setup.c deleted in HEAD and modified in quilt/rr. Version quilt/rr of arch/x86/mach-voyager/setup.c left in tree. CONFLICT (content): Merge conflict in drivers/firmware/dcdbas.c CONFLICT (content): Merge conflict in drivers/hid/hid-core.c CONFLICT (content): Merge conflict in drivers/media/video/saa7134/saa7134-core.c CONFLICT (content): Merge conflict in drivers/media/video/saa7134/saa7134.h CONFLICT (content): Merge conflict in drivers/net/virtio_net.c CONFLICT (content): Merge conflict in kernel/module.c $ git rm -f arch/x86/mach-default/setup.c $ git rm -f arch/x86/mach-voyager/setup.c Applying: rr: x86 irqaction merge fixup Merging cifs/master Merging mmc/next Merging gfs2/master Merging input/next Merging bkl-removal/bkl-removal Merging ubifs/linux-next Merging lsm/for-next Merging block/for-next Merging embedded/master Merging firmware/master CONFLICT (content): Merge conflict in firmware/Makefile CONFLICT (content): Merge conflict in firmware/WHENCE CONFLICT (content): Merge conflict in sound/isa/Kconfig Merging pcmcia/master Merging battery/master Merging leds/for-mm Merging backlight/for-mm Merging kgdb/kgdb-next Merging slab/for-next CONFLICT (content): Merge conflict in include/linux/rcupdate.h CONFLICT (content): Merge conflict in include/linux/slub_def.h CONFLICT (content): Merge conflict in mm/slob.c CONFLICT (content): Merge conflict in mm/slub.c Merging uclinux/for-next Merging md/for-next $ git reset --hard HEAD^ Merging next-20090306/md Merging mfd/for-next Merging hdlc/hdlc-next Merging drm/drm-next CONFLICT (content): Merge conflict in drivers/gpu/drm/drm_proc.c Merging voltage/for-next Merging security-testing/next Merging lblnet/master Merging quilt/ttydev Merging agp/agp-next Merging kmemcheck/auto-kmemcheck-next CONFLICT (content): Merge conflict in MAINTAINERS CONFLICT (content): Merge conflict in arch/x86/Kconfig CONFLICT (content): Merge conflict in arch/x86/mm/init_32.c CONFLICT (content): Merge conflict in arch/x86/mm/init_64.c CONFLICT (content): Merge conflict in kernel/trace/ring_buffer.c CONFLICT (content): Merge conflict in mm/Makefile Applying: kmemcheck: arcgh/x86/mm/init.c merge fix Merging generic-ipi/auto-generic-ipi-next Merging oprofile/auto-oprofile-next Merging fastboot/auto-fastboot-next Merging sparseirq/auto-sparseirq-next Merging iommu/auto-iommu-next Merging uwb/for-upstream Merging watchdog/master Merging proc/proc CONFLICT (content): Merge conflict in security/selinux/hooks.c Merging bdev/master Merging dwmw2-iommu/master Merging cputime/cputime Merging osd/linux-next CONFLICT (add/add): Merge conflict in drivers/scsi/osd/osd_initiator.c Merging fatfs/master Merging fuse/for-next Merging jc_docs/docs-next Merging nommu/master Merging trivial/for-next Merging audit/for-next Merging squashfs/master Merging omap/for-next Merging quilt/aoe Merging kmemleak/kmemleak CONFLICT (content): Merge conflict in Documentation/kernel-parameters.txt CONFLICT (content): Merge conflict in MAINTAINERS CONFLICT (content): Merge conflict in include/linux/percpu.h CONFLICT (content): Merge conflict in include/linux/slab.h CONFLICT (content): Merge conflict in init/main.c CONFLICT (content): Merge conflict in kernel/module.c CONFLICT (content): Merge conflict in lib/Kconfig.debug CONFLICT (content): Merge conflict in mm/slab.c CONFLICT (content): Merge conflict in mm/slob.c CONFLICT (content): Merge conflict in mm/slub.c CONFLICT (content): Merge conflict in mm/vmalloc.c Merging quilt/driver-core CONFLICT (content): Merge conflict in drivers/media/video/v4l2-device.c CONFLICT (content): Merge conflict in drivers/net/wimax/i2400m/usb-notif.c CONFLICT (content): Merge conflict in drivers/sh/maple/maple.c Applying: acpi: update thermal for bus_id removal Applying: crypto: remove pr_fmt for now Merging quilt/usb Merging quilt/staging Merging scsi-post-merge/master Applying: proc: remove a new user of proc_dir_entry::owner [-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --] ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (staging/multimedia) 2009-03-11 11:59 linux-next: Tree for March 11 Stephen Rothwell @ 2009-03-11 17:12 ` Randy Dunlap 2009-03-11 18:11 ` Greg KH 2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap 1 sibling, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-11 17:12 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML, Greg KH, linux-media Stephen Rothwell wrote: > Hi all, > > Changes since 20090310: drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' undeclared here (not in a function) -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (staging/multimedia) 2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap @ 2009-03-11 18:11 ` Greg KH 2009-03-11 18:21 ` Randy Dunlap 0 siblings, 1 reply; 16+ messages in thread From: Greg KH @ 2009-03-11 18:11 UTC (permalink / raw) To: Randy Dunlap; +Cc: Stephen Rothwell, linux-next, LKML, linux-media On Wed, Mar 11, 2009 at 10:12:39AM -0700, Randy Dunlap wrote: > Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20090310: > > > drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' undeclared here (not in a function) Odd, nothing has changed in this driver, is this a v4l api change? thanks, greg k-h ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (staging/multimedia) 2009-03-11 18:11 ` Greg KH @ 2009-03-11 18:21 ` Randy Dunlap 2009-03-11 18:24 ` Greg KH 2009-03-11 18:27 ` Hans Verkuil 0 siblings, 2 replies; 16+ messages in thread From: Randy Dunlap @ 2009-03-11 18:21 UTC (permalink / raw) To: Greg KH; +Cc: Stephen Rothwell, linux-next, LKML, linux-media Greg KH wrote: > On Wed, Mar 11, 2009 at 10:12:39AM -0700, Randy Dunlap wrote: >> Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20090310: >> >> drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' undeclared here (not in a function) > > Odd, nothing has changed in this driver, is this a v4l api change? I don't know if the vl4 API changed, but this error has been around for some time now. Just because it's just now being reported is one change. Surely other people build these drivers. ??? I do know that other video drivers (with one exception) don't set: .vfl_type = VID_TYPE_CAPTURE, at all, so maybe it's not needed (?). -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (staging/multimedia) 2009-03-11 18:21 ` Randy Dunlap @ 2009-03-11 18:24 ` Greg KH 2009-03-11 18:27 ` Hans Verkuil 1 sibling, 0 replies; 16+ messages in thread From: Greg KH @ 2009-03-11 18:24 UTC (permalink / raw) To: Randy Dunlap; +Cc: Stephen Rothwell, linux-next, LKML, linux-media On Wed, Mar 11, 2009 at 11:21:52AM -0700, Randy Dunlap wrote: > Greg KH wrote: > > On Wed, Mar 11, 2009 at 10:12:39AM -0700, Randy Dunlap wrote: > >> Stephen Rothwell wrote: > >>> Hi all, > >>> > >>> Changes since 20090310: > >> > >> drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' undeclared here (not in a function) > > > > Odd, nothing has changed in this driver, is this a v4l api change? > > I don't know if the vl4 API changed, but this error has been around > for some time now. Just because it's just now being reported is one > change. Surely other people build these drivers. ??? I do, and don't seem to get this error. Ah, it's a CONFIG_VIDEO_V4L1_COMPAT issue. I'll see what needs to do to fix this up. thanks, greg k-h ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (staging/multimedia) 2009-03-11 18:21 ` Randy Dunlap 2009-03-11 18:24 ` Greg KH @ 2009-03-11 18:27 ` Hans Verkuil 1 sibling, 0 replies; 16+ messages in thread From: Hans Verkuil @ 2009-03-11 18:27 UTC (permalink / raw) To: Randy Dunlap; +Cc: Greg KH, Stephen Rothwell, linux-next, LKML, linux-media On Wednesday 11 March 2009 19:21:52 Randy Dunlap wrote: > Greg KH wrote: > > On Wed, Mar 11, 2009 at 10:12:39AM -0700, Randy Dunlap wrote: > >> Stephen Rothwell wrote: > >>> Hi all, > >>> > >>> Changes since 20090310: > >> > >> drivers/staging/go7007/go7007-v4l2.c:1830: error: 'VID_TYPE_CAPTURE' > >> undeclared here (not in a function) > > > > Odd, nothing has changed in this driver, is this a v4l api change? > > I don't know if the vl4 API changed, but this error has been around > for some time now. Just because it's just now being reported is one > change. Surely other people build these drivers. ??? > > > I do know that other video drivers (with one exception) don't set: > .vfl_type = VID_TYPE_CAPTURE, > at all, so maybe it's not needed (?). That's correct, this assignment isn't needed. The error appears now since VID_TYPE_CAPTURE has been made inaccessible for V4L2 drivers. Only old V4L1 drivers can use it. This change was very recent and before that it compiled fine. Although even then that code was wrong (but harmless). Just remove that line and it will compile fine again. Although unless someone will take this driver to the next level it will probably break again once the old autoprobing i2c API is removed (and that's slated for 2.6.30 if all goes well). Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-11 11:59 linux-next: Tree for March 11 Stephen Rothwell 2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap @ 2009-03-11 17:36 ` Randy Dunlap 2009-03-12 16:17 ` Randy Dunlap 1 sibling, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-11 17:36 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML Stephen Rothwell wrote: > Hi all, > > Changes since 20090310: Building on i386 generates a ton of printk format warnings: kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' include/trace/sched_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:31: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:31: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:41: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:41: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:53: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:53: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:65: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:65: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:85: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:85: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:98: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:98: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:108: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:108: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:118: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:118: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:128: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:128: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/sched_event_types.h:140: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/sched_event_types.h:140: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/irq_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/irq_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' include/trace/irq_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' include/trace/irq_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:8: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:8: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:16: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:16: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:25: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:25: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:34: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:34: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:47: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:47: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:60: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:60: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:75: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:75: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:90: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:90: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:105: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:105: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:114: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:114: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:124: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:124: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:132: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:132: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:142: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:142: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' kernel/trace/trace_event_types.h:156: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' kernel/trace/trace_event_types.h:156: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap @ 2009-03-12 16:17 ` Randy Dunlap 2009-03-12 16:26 ` Steven Rostedt 0 siblings, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-12 16:17 UTC (permalink / raw) To: Stephen Rothwell Cc: linux-next, LKML, Frederic Weisbecker, Steven Rostedt, Ingo Molnar [adding cc:s] [same report for March 12] Randy Dunlap wrote: > Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20090310: > > > Building on i386 generates a ton of printk format warnings: > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > > include/trace/sched_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:31: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:31: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:41: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:41: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:53: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:53: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:65: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:65: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:85: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:85: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:98: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:98: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:108: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:108: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:118: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:118: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:128: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:128: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/sched_event_types.h:140: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/sched_event_types.h:140: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > > include/trace/irq_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/irq_event_types.h:11: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > include/trace/irq_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > include/trace/irq_event_types.h:21: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > > kernel/trace/trace_event_types.h:8: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:8: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:16: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:16: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:25: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:25: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:34: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:34: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:47: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:47: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:60: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:60: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:75: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:75: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:90: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:90: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:105: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:105: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:114: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:114: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:124: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:124: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:132: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:132: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:142: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:142: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' > kernel/trace/trace_event_types.h:156: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'unsigned int' > kernel/trace/trace_event_types.h:156: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int' -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-12 16:17 ` Randy Dunlap @ 2009-03-12 16:26 ` Steven Rostedt 2009-03-12 16:32 ` Randy Dunlap 2009-03-18 15:46 ` Randy Dunlap 0 siblings, 2 replies; 16+ messages in thread From: Steven Rostedt @ 2009-03-12 16:26 UTC (permalink / raw) To: Randy Dunlap Cc: Stephen Rothwell, linux-next, LKML, Frederic Weisbecker, Ingo Molnar On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: > [adding cc:s] > > [same report for March 12] > > Randy Dunlap wrote: > > Stephen Rothwell wrote: > >> Hi all, > >> > >> Changes since 20090310: > > > > > > Building on i386 generates a ton of printk format warnings: > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > > I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to handle the "sizeof()" case. The fix was suggested by Andrew Morton. -- Steve ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-12 16:26 ` Steven Rostedt @ 2009-03-12 16:32 ` Randy Dunlap 2009-03-18 15:46 ` Randy Dunlap 1 sibling, 0 replies; 16+ messages in thread From: Randy Dunlap @ 2009-03-12 16:32 UTC (permalink / raw) To: Steven Rostedt Cc: Stephen Rothwell, linux-next, LKML, Frederic Weisbecker, Ingo Molnar Steven Rostedt wrote: > On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: >> [adding cc:s] >> >> [same report for March 12] >> >> Randy Dunlap wrote: >>> Stephen Rothwell wrote: >>>> Hi all, >>>> >>>> Changes since 20090310: >>> >>> Building on i386 generates a ton of printk format warnings: >>> >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' >>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' >>> > > I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to > handle the "sizeof()" case. The fix was suggested by Andrew Morton. OK, thanks for the info. -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-12 16:26 ` Steven Rostedt 2009-03-12 16:32 ` Randy Dunlap @ 2009-03-18 15:46 ` Randy Dunlap 2009-03-18 16:06 ` Ingo Molnar 1 sibling, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-18 15:46 UTC (permalink / raw) To: Steven Rostedt Cc: Stephen Rothwell, linux-next, LKML, Frederic Weisbecker, Ingo Molnar On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: > > On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: > > [adding cc:s] > > > > [same report for March 12] > > > > Randy Dunlap wrote: > > > Stephen Rothwell wrote: > > >> Hi all, > > >> > > >> Changes since 20090310: > > > > > > > > > Building on i386 generates a ton of printk format warnings: > > > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > > > > > I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to > handle the "sizeof()" case. The fix was suggested by Andrew Morton. This build warning is still around (20090318). Is the fix not in some branch that is imported into linux-next or what? Thanks, --- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-18 15:46 ` Randy Dunlap @ 2009-03-18 16:06 ` Ingo Molnar 2009-03-18 16:13 ` Randy Dunlap 0 siblings, 1 reply; 16+ messages in thread From: Ingo Molnar @ 2009-03-18 16:06 UTC (permalink / raw) To: Randy Dunlap Cc: Steven Rostedt, Stephen Rothwell, linux-next, LKML, Frederic Weisbecker * Randy Dunlap <randy.dunlap@oracle.com> wrote: > On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: > > > > > On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: > > > [adding cc:s] > > > > > > [same report for March 12] > > > > > > Randy Dunlap wrote: > > > > Stephen Rothwell wrote: > > > >> Hi all, > > > >> > > > >> Changes since 20090310: > > > > > > > > > > > > Building on i386 generates a ton of printk format warnings: > > > > > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > > > > kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > > > > > > > > I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to > > handle the "sizeof()" case. The fix was suggested by Andrew Morton. > > > This build warning is still around (20090318). > Is the fix not in some branch that is imported into linux-next or what? be patient. Ingo ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-18 16:06 ` Ingo Molnar @ 2009-03-18 16:13 ` Randy Dunlap 2009-03-18 16:32 ` Ingo Molnar 0 siblings, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-18 16:13 UTC (permalink / raw) To: Ingo Molnar Cc: Steven Rostedt, Stephen Rothwell, linux-next, LKML, Frederic Weisbecker Ingo Molnar wrote: > * Randy Dunlap <randy.dunlap@oracle.com> wrote: > >> On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: >> >>> On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: >>>> [adding cc:s] >>>> >>>> [same report for March 12] >>>> >>>> Randy Dunlap wrote: >>>>> Stephen Rothwell wrote: >>>>>> Hi all, >>>>>> >>>>>> Changes since 20090310: >>>>> >>>>> Building on i386 generates a ton of printk format warnings: >>>>> >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' >>>>> >>> I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to >>> handle the "sizeof()" case. The fix was suggested by Andrew Morton. >> >> This build warning is still around (20090318). >> Is the fix not in some branch that is imported into linux-next or what? > > be patient. > > Ingo I think that 7 days is being patient for a simple build fix. Thanks. -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-18 16:13 ` Randy Dunlap @ 2009-03-18 16:32 ` Ingo Molnar 2009-03-18 16:44 ` Randy Dunlap 0 siblings, 1 reply; 16+ messages in thread From: Ingo Molnar @ 2009-03-18 16:32 UTC (permalink / raw) To: Randy Dunlap Cc: Steven Rostedt, Stephen Rothwell, linux-next, LKML, Frederic Weisbecker * Randy Dunlap <randy.dunlap@oracle.com> wrote: > Ingo Molnar wrote: > > * Randy Dunlap <randy.dunlap@oracle.com> wrote: > > > >> On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: > >> > >>> On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: > >>>> [adding cc:s] > >>>> > >>>> [same report for March 12] > >>>> > >>>> Randy Dunlap wrote: > >>>>> Stephen Rothwell wrote: > >>>>>> Hi all, > >>>>>> > >>>>>> Changes since 20090310: > >>>>> > >>>>> Building on i386 generates a ton of printk format warnings: > >>>>> > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > >>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > >>>>> > >>> I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to > >>> handle the "sizeof()" case. The fix was suggested by Andrew Morton. > >> > >> This build warning is still around (20090318). > >> Is the fix not in some branch that is imported into linux-next or what? > > > > be patient. > > > > Ingo > > I think that 7 days is being patient for a simple build fix. s/build fix/harmless build warning fix If you are interested in having a resolution you can git-merge the latest development tree yourself and you can get rid of that warning. Of course that way you'd expose yourself to even fresher code, potentially with much more serious breakages. It's a balance of freshness versus stability, and that balance is kept by maintainers. If you want the latest development code - go engage with the development trees directly. If you want something that is relatively new (i.e. 1-2 weeks fresh) but works on the range of systems we test, use what you get in linux-next. It's your choice which one you pick. But you cannot have both. If you genuinely think you can have it both, by all means i encourage you to try it - it's all open source so you can run your own tree. Just please dont feel entitled to demand it from others. Ingo ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-18 16:32 ` Ingo Molnar @ 2009-03-18 16:44 ` Randy Dunlap 2009-03-18 16:49 ` Ingo Molnar 0 siblings, 1 reply; 16+ messages in thread From: Randy Dunlap @ 2009-03-18 16:44 UTC (permalink / raw) To: Ingo Molnar Cc: Steven Rostedt, Stephen Rothwell, linux-next, LKML, Frederic Weisbecker Ingo Molnar wrote: > * Randy Dunlap <randy.dunlap@oracle.com> wrote: > >> Ingo Molnar wrote: >>> * Randy Dunlap <randy.dunlap@oracle.com> wrote: >>> >>>> On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: >>>> >>>>> On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: >>>>>> [adding cc:s] >>>>>> >>>>>> [same report for March 12] >>>>>> >>>>>> Randy Dunlap wrote: >>>>>>> Stephen Rothwell wrote: >>>>>>>> Hi all, >>>>>>>> >>>>>>>> Changes since 20090310: >>>>>>> Building on i386 generates a ton of printk format warnings: >>>>>>> >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' >>>>>>> >>>>> I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to >>>>> handle the "sizeof()" case. The fix was suggested by Andrew Morton. >>>> This build warning is still around (20090318). >>>> Is the fix not in some branch that is imported into linux-next or what? >>> be patient. >>> >>> Ingo >> I think that 7 days is being patient for a simple build fix. > > s/build fix/harmless build warning fix 180+ lines of noise in a build log. > If you are interested in having a resolution you can git-merge the > latest development tree yourself and you can get rid of that > warning. > > Of course that way you'd expose yourself to even fresher code, > potentially with much more serious breakages. > > It's a balance of freshness versus stability, and that balance is > kept by maintainers. > > If you want the latest development code - go engage with the > development trees directly. > > If you want something that is relatively new (i.e. 1-2 weeks fresh) > but works on the range of systems we test, use what you get in > linux-next. > > It's your choice which one you pick. > > But you cannot have both. > > If you genuinely think you can have it both, by all means i > encourage you to try it - it's all open source so you can run your > own tree. Just please dont feel entitled to demand it from others. Thanks for the explanation. That's what I tried to ask for to begin with. I guess that I have a language problem. -- ~Randy ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: linux-next: Tree for March 11 (tracing) 2009-03-18 16:44 ` Randy Dunlap @ 2009-03-18 16:49 ` Ingo Molnar 0 siblings, 0 replies; 16+ messages in thread From: Ingo Molnar @ 2009-03-18 16:49 UTC (permalink / raw) To: Randy Dunlap Cc: Steven Rostedt, Stephen Rothwell, linux-next, LKML, Frederic Weisbecker * Randy Dunlap <randy.dunlap@oracle.com> wrote: > Ingo Molnar wrote: > > * Randy Dunlap <randy.dunlap@oracle.com> wrote: > > > >> Ingo Molnar wrote: > >>> * Randy Dunlap <randy.dunlap@oracle.com> wrote: > >>> > >>>> On Thu, 12 Mar 2009 12:26:21 -0400 Steven Rostedt wrote: > >>>> > >>>>> On Thu, 2009-03-12 at 09:17 -0700, Randy Dunlap wrote: > >>>>>> [adding cc:s] > >>>>>> > >>>>>> [same report for March 12] > >>>>>> > >>>>>> Randy Dunlap wrote: > >>>>>>> Stephen Rothwell wrote: > >>>>>>>> Hi all, > >>>>>>>> > >>>>>>>> Changes since 20090310: > >>>>>>> Building on i386 generates a ton of printk format warnings: > >>>>>>> > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 5 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 6 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 9 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 10 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 13 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 14 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 17 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 18 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 21 has type 'unsigned int' > >>>>>>> kernel/trace/trace_events.c:470: warning: format '%lu' expects type 'long unsigned int', but argument 22 has type 'unsigned int' > >>>>>>> > >>>>> I believe this is corrected in Ingo's tip tree. I changed %lu to %zu to > >>>>> handle the "sizeof()" case. The fix was suggested by Andrew Morton. > >>>> This build warning is still around (20090318). > >>>> Is the fix not in some branch that is imported into linux-next or what? > >>> be patient. > >>> > >>> Ingo > >> I think that 7 days is being patient for a simple build fix. > > > > s/build fix/harmless build warning fix > > 180+ lines of noise in a build log. > > > If you are interested in having a resolution you can git-merge the > > latest development tree yourself and you can get rid of that > > warning. > > > > Of course that way you'd expose yourself to even fresher code, > > potentially with much more serious breakages. > > > > It's a balance of freshness versus stability, and that balance is > > kept by maintainers. > > > > If you want the latest development code - go engage with the > > development trees directly. > > > > If you want something that is relatively new (i.e. 1-2 weeks fresh) > > but works on the range of systems we test, use what you get in > > linux-next. > > > > It's your choice which one you pick. > > > > But you cannot have both. > > > > If you genuinely think you can have it both, by all means i > > encourage you to try it - it's all open source so you can run your > > own tree. Just please dont feel entitled to demand it from others. > > Thanks for the explanation. That's what I tried to ask for > to begin with. I guess that I have a language problem. Note, six hours ago i reintegrated all the auto-next branches so this warning should be gone in the next linux-next iteration - they are now traded for brand new bugs ;-) Ingo ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2009-03-18 16:49 UTC | newest] Thread overview: 16+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-03-11 11:59 linux-next: Tree for March 11 Stephen Rothwell 2009-03-11 17:12 ` linux-next: Tree for March 11 (staging/multimedia) Randy Dunlap 2009-03-11 18:11 ` Greg KH 2009-03-11 18:21 ` Randy Dunlap 2009-03-11 18:24 ` Greg KH 2009-03-11 18:27 ` Hans Verkuil 2009-03-11 17:36 ` linux-next: Tree for March 11 (tracing) Randy Dunlap 2009-03-12 16:17 ` Randy Dunlap 2009-03-12 16:26 ` Steven Rostedt 2009-03-12 16:32 ` Randy Dunlap 2009-03-18 15:46 ` Randy Dunlap 2009-03-18 16:06 ` Ingo Molnar 2009-03-18 16:13 ` Randy Dunlap 2009-03-18 16:32 ` Ingo Molnar 2009-03-18 16:44 ` Randy Dunlap 2009-03-18 16:49 ` Ingo Molnar
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).