linux-next: Tree for October 13
Subsystems (7)
Hi all,
Changes since 20101012:
The i.MX tree lost its conflicts.
The drm tree gained a conflict against the kgdb tree.
The usb tree gained a build failure (due to an interaction with the scsi tree) for which I applied a patch.
The bkl-llseek tree gained a conflict against the infiniband tree.
----------------------------------------------------------------------------
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 176 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 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 · 252 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/mach-at91/include/mach/system.h CONFLICT (content): Merge conflict in arch/arm/mach-imx/mach-cpuimx27.c 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 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 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 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 hfsplus/for-next 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 Applying: xfs: fix up mismerge of __xfs_inode_clear_reclaim_tag Merging vfs/for-next Merging pci/linux-next Merging hid/for-next Merging quilt/i2c Merging bjdooks-i2c/next-i2c Merging quilt/jdelvare-hwmon Merging hwmon-staging/hwmon-next Merging quilt/kernel-doc 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 CONFLICT (content): Merge conflict in arch/x86/kvm/svm.c CONFLICT (content): Merge conflict in virt/kvm/kvm_main.c Merging dlm/next Merging swiotlb/master Merging swiotlb-xen/master Merging ibft/master Merging scsi/master Merging async_tx/next Merging wireless/master CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-omap3pandora.c CONFLICT (content): Merge conflict in arch/arm/mach-omap2/board-zoom-peripherals.c CONFLICT (content): Merge conflict in drivers/net/wireless/libertas/if_sdio.c Merging net/master CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt CONFLICT (delete/modify): drivers/ieee1394/eth1394.c deleted in HEAD and modified in net/master. Version net/master of drivers/ieee1394/eth1394.c left in tree. $ git rm -f drivers/ieee1394/eth1394.c Merging mtd/master Merging crypto/master CONFLICT (content): Merge conflict in arch/arm/mach-omap2/devices.c Merging sound-asoc/for-next CONFLICT (content): Merge conflict in arch/arm/mach-s3c64xx/dev-audio.c CONFLICT (content): Merge conflict in drivers/video/sh_mobile_hdmi.c Merging sound/for-next Merging cpufreq/next Merging quilt/rr Merging input/next CONFLICT (content): Merge conflict in drivers/input/keyboard/Kconfig Merging lsm/for-next Merging block/for-next CONFLICT (content): Merge conflict in fs/ext4/mballoc.c Applying: ext4: merge fix for blkdev_issue_zeroout API change Merging quilt/device-mapper Merging embedded/master Merging firmware/master Merging pcmcia/master CONFLICT (content): Merge conflict in drivers/net/pcmcia/smc91c92_cs.c Merging battery/master Merging leds/for-mm Merging backlight/for-mm Merging mmc/mmc-next Merging kgdb/kgdb-next CONFLICT (content): Merge conflict in drivers/char/sysrq.c Merging slab/for-next Merging uclinux/for-next Merging md/for-next Merging mfd/for-next CONFLICT (content): Merge conflict in drivers/mfd/sh_mobile_sdhi.c Merging hdlc/hdlc-next Merging drm/drm-next CONFLICT (content): Merge conflict in drivers/gpu/drm/drm_fb_helper.c CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.c CONFLICT (content): Merge conflict in drivers/gpu/drm/nouveau/nv04_crtc.c CONFLICT (content): Merge conflict in drivers/gpu/drm/nouveau/nv50_crtc.c CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/atombios_crtc.c CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/radeon_legacy_crtc.c CONFLICT (content): Merge conflict in drivers/gpu/drm/radeon/radeon_mode.h CONFLICT (content): Merge conflict in include/drm/drm_crtc_helper.h 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 net/irda/irnet/irnet_ppp.c Merging audit/for-next Merging quilt/aoe Merging suspend/linux-next Merging bluetooth/master Merging fsnotify/for-next Merging irda/for-next Merging catalin/for-next CONFLICT (content): Merge conflict in arch/arm/kernel/Makefile CONFLICT (content): Merge conflict in arch/arm/mach-vexpress/ct-ca9x4.c CONFLICT (content): Merge conflict in arch/arm/mm/flush.c Merging alacrity/linux-next CONFLICT (content): Merge conflict in include/linux/Kbuild Merging i7core_edac/linux_next CONFLICT (content): Merge conflict in MAINTAINERS Merging i7300_edac/linux_next Merging devicetree/next-devicetree Merging spi/next-spi Merging omap_dss2/for-next Merging xen/upstream/xen Merging rcu/rcu/next Merging tip/auto-latest CONFLICT (content): Merge conflict in include/linux/percpu.h CONFLICT (content): Merge conflict in net/core/dev.c Merging edac-amd/for-next Merging oprofile/for-next CONFLICT (content): Merge conflict in arch/arm/oprofile/common.c CONFLICT (content): Merge conflict in kernel/perf_event.c Applying: perf events: fix up merge conflict Merging percpu/for-next CONFLICT (content): Merge conflict in include/linux/percpu.h CONFLICT (content): Merge conflict in mm/percpu.c Merging workqueues/for-next CONFLICT (content): Merge conflict in fs/gfs2/main.c Merging sfi/sfi-test Merging asm-generic/next Merging drivers-x86/linux-next Merging hwpoison/hwpoison Merging sysctl/master Merging quilt/driver-core CONFLICT (content): Merge conflict in drivers/misc/Makefile Merging quilt/tty Merging quilt/usb CONFLICT (content): Merge conflict in drivers/usb/gadget/rndis.c Merging staging-next/staging-next CONFLICT (rename/modify): Merge conflict in drivers/misc/ti-st/st_kim.c CONFLICT (content): Merge conflict in arch/arm/plat-omap/devices.c CONFLICT (content): Merge conflict in drivers/misc/Makefile CONFLICT (content): Merge conflict in drivers/staging/Makefile CONFLICT (content): Merge conflict in drivers/staging/batman-adv/hard-interface.c CONFLICT (delete/modify): drivers/staging/mrst-touchscreen/Makefile deleted in HEAD and modified in staging-next/staging-next. Version staging-next/staging-next of drivers/staging/mrst-touchscreen/Makefile left in tree. CONFLICT (delete/modify): drivers/staging/mrst-touchscreen/intel-mid-touch.c deleted in HEAD and modified in staging-next/staging-next. Version staging-next/staging-next of drivers/staging/mrst-touchscreen/intel-mid-touch.c left in tree. CONFLICT (delete/modify): drivers/staging/ti-st/st.h deleted in staging-next/staging-next and modified in HEAD. Version HEAD of drivers/staging/ti-st/st.h left in tree. CONFLICT (delete/modify): drivers/staging/ti-st/st_core.h deleted in staging-next/staging-next and modified in HEAD. Version HEAD of drivers/staging/ti-st/st_core.h left in tree. $ git rm -f drivers/staging/mrst-touchscreen/Makefile drivers/staging/mrst-touchscreen/intel-mid-touch.c $ git rm -f drivers/staging/ti-st/st.h drivers/staging/ti-st/st_core.h Applying: staging: ath6kl: Fixing the driver to use modified mmc_host structure Applying: scsi/sd: update for hw_sector_size rename Merging slabh/slabh Merging bkl-trivial/trivial CONFLICT (content): Merge conflict in drivers/block/ataflop.c CONFLICT (content): Merge conflict in drivers/char/pcmcia/cm4000_cs.c CONFLICT (content): Merge conflict in drivers/char/pcmcia/cm4040_cs.c CONFLICT (content): Merge conflict in drivers/mmc/card/block.c Merging bkl-llseek/llseek CONFLICT (content): Merge conflict in drivers/gpu/drm/vmwgfx/vmwgfx_drv.c CONFLICT (content): Merge conflict in drivers/infiniband/hw/cxgb4/device.c Merging bkl-vfs/vfs CONFLICT (content): Merge conflict in fs/cifs/cifsfs.c CONFLICT (content): Merge conflict in fs/nilfs2/super.c Merging bkl-config/config CONFLICT (content): Merge conflict in fs/compat_ioctl.c Merging irqflags/master Merging cleancache/linux-next CONFLICT (content): Merge conflict in include/linux/fs.h CONFLICT (content): Merge conflict in mm/Kconfig Merging scsi-post-merge/merge-base:master
Re: linux-next: Tree for October 13 (net/3c59x)
Quoted 3 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Hi all,
Changes since 20101012:
when CONFIG_PCI is not enabled:
drivers/net/3c59x.c:3211: error:request for member 'current_state' in something not a structure or union
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
David Miller
maintainerRe: linux-next: Tree for October 13 (net/3c59x)
From: Randy Dunlap <[email protected]>
Date: Wed, 13 Oct 2010 09:38:36 -0700
Quoted 10 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Quoted 4 lines
Hi all,
Changes since 20101012:
when
CONFIG_PCIis not enabled:
drivers/net/3c59x.c:3211: error:request for member 'current_state' in something not a structure or union
Like all the other PCI interfaces that NOP out into empty inlines when CONFIG_PCI is not enabled, it would be nice to have an interface that provides pci_dev->current_state in a similar fashion so we don't have to add a bunch of ifdefs here.
Re: linux-next: Tree for October 13 (staging/iio)
In reply to Stephen RothwellQuoted 3 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Hi all,
Changes since 20101012:
drivers/staging/iio/adc/ad7476.h:62: note: expected 'struct device *' but argument is of type 'struct ad7476_state *' drivers/staging/iio/adc/ad7476_core.c:48: error: too few arguments to function 'ad7476_scan_from_ring' drivers/staging/iio/adc/ad7476_core.c: At top level:drivers/staging/iio/adc/ad7476_core.c:102: error: 'IIO_SCAN_EL_TYPE_UNSIGNED' undeclared here (not in a function)
config is attached.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
RE: linux-next: Tree for October 13 (staging/iio)
Randy Dunlap wrote on 2010-10-13:
Quoted 11 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Quoted 4 lines
Hi all,
Changes since 20101012:
drivers/staging/iio/adc/ad7476.h:62: note: expected 'struct device *' but argument is of type 'structad7476_state*'drivers/staging/iio/adc/ad7476_core.c:48: error: too few arguments to function 'ad7476_scan_from_ring'
Thanks!
That's due to an old prototype active when CONFIG_IIO_RING_BUFFER is not se= t.
I'll fix that.
Quoted 3 lines
drivers/staging/iio/adc/ad7476_core.c: At top level:drivers/staging/iio/adc/ad7476_core.c:102: error:
'IIO_SCAN_EL_TYPE_UNSIGNED' undeclared here (not in a function)
Jonathan,
Do we really need to guard the entire ring_generic.h header with
#ifdef CONFIG_IIO_RING_BUFFER
...
Some of these might be used, even when CONFIG_IIO_RING_BUFFER is not set. Or do we really need CONFIG_IIO_RING_BUFFER at all.
Why not always provide it?
Quoted 7 lines
config is attached.
---
~Randy
*** Remember to useDocumentation/SubmitChecklistwhen testing your code ***
Greetings,
Michael
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036 Geschaeft= sfuehrer Thomas Wessel, William A. Martin, Margaret Seif
Re: linux-next: Tree for October 13 (staging/iio)
Quoted 24 lines · Michael
Randy Dunlap wrote on 2010-10-13:
Quoted 11 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Quoted 4 lines
Hi all,
Changes since 20101012:
drivers/staging/iio/adc/ad7476.h:62: note: expected 'struct device *' but argument is of type 'structad7476_state*'drivers/staging/iio/adc/ad7476_core.c:48: error: too few arguments to function 'ad7476_scan_from_ring'Thanks!
That's due to an old prototype active when
CONFIG_IIO_RING_BUFFERis not set. I'll fix that.Quoted 3 lines
drivers/staging/iio/adc/ad7476_core.c: At top level:drivers/staging/iio/adc/ad7476_core.c:102: error:
'IIO_SCAN_EL_TYPE_UNSIGNED' undeclared here (not in a function)Jonathan,
Quoted 8 lines
Do we really need to guard the entire
ring_generic.hheader with#ifdef
CONFIG_IIO_RING_BUFFER
...Some of these might be used, even when
CONFIG_IIO_RING_BUFFERis not set. Or do we really needCONFIG_IIO_RING_BUFFERat all.
Why not always provide it?
It's a fairly big chunk of code and I suspect a fair few of our users (all the light sensors for starters) won't want it at all. If anything I'm keen to do a bit of reorganization of other bits of the core to further cut down on the minimum present.
Move relevant functions out as needed or put stubs in place. Perhaps we can revisiting this question down the line, but I don't think we want to make buffer support obligatory at the moment.
Jonathan
Quoted 17 lines
Quoted 8 lines
config is attached.
---
~Randy
*** Remember to useDocumentation/SubmitChecklistwhen testing your code ***Greetings,
MichaelAnalog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
PATCH 1/1 gpu/drm: fix build errors and kconfig dependency warnings
In reply to Stephen RothwellQuoted 5 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell wrote:
Hi all,
Changes since 20101012:
The drm tree gained a conflict against the kgdb tree.
ERROR: "hwmon_device_unregister" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
ERROR: "hwmon_device_register" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
ERROR: "video_output_unregister" [drivers/acpi/video.ko] undefined!
ERROR: "video_output_register" [drivers/acpi/video.ko] undefined!
The latter 2 are simple to fix:
in drivers/gpu/drm/nouveau/Kconfig, for config DRM_NOUVEAU:
@@ -11,6 +11,7 @@ config DRM_NOUVEAU
select FRAMEBUFFER_CONSOLE if !EMBEDDED select FB_BACKLIGHT if DRM_NOUVEAU_BACKLIGHT select ACPI_VIDEO if ACPI
+ select VIDEO_OUTPUT_CONTROL if ACPI
help
Choose this option for open-source nVidia support.
The first 2 are a problem. I'd like to add "depends on HWMON" to DRM_NOUVEAU, but doing so gives:
drivers/video/Kconfig:30:error: recursive dependency detected!drivers/video/Kconfig:30: symbol FB is selected by DRM_KMS_HELPERdrivers/gpu/drm/Kconfig:22: symbol DRM_KMS_HELPER is selected by DRM_NOUVEAUdrivers/gpu/drm/nouveau/Kconfig:1: symbol DRM_NOUVEAU depends on HWMONdrivers/hwmon/Kconfig:5: symbol HWMON is selected by THINKPAD_ACPIdrivers/platform/x86/Kconfig:232: symbol THINKPAD_ACPI depends on INPUTdrivers/input/Kconfig:8: symbol INPUT is selected by VTdrivers/char/Kconfig:7: symbol VT is selected by FB_STIdrivers/video/Kconfig:636: symbol FB_STI depends on FB
so that must not be the right thing to do. Aha, that change along with changing all "select FB" (in drivers/gpu/drm/*) to "depends on FB" fixes the kconfig warnings. But feel free to fix it some other way.
My working patch is below.
---
From: Randy Dunlap <[email protected]>
Fix drm and drm/nouveau kconfigs so that build succeeds and kconfig warnings are eliminated.
Fixes these build errors:
ERROR: "hwmon_device_unregister" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
ERROR: "hwmon_device_register" [drivers/gpu/drm/nouveau/nouveau.ko] undefined!
ERROR: "video_output_unregister" [drivers/acpi/video.ko] undefined!
ERROR: "video_output_register" [drivers/acpi/video.ko] undefined!
--- drivers/gpu/drm/Kconfig | 2 +- drivers/gpu/drm/nouveau/Kconfig | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-)
drivers/gpu/drm/nouveau/Kconfig +3 -2
@@ -1,16 +1,17 @@ config DRM_NOUVEAU tristate "Nouveau (nVidia) cards" - depends on DRM && PCI + depends on DRM && PCI && HWMON + depends on FB select FW_LOADER select DRM_KMS_HELPER select DRM_TTM select FB_CFB_FILLRECT select FB_CFB_COPYAREA select FB_CFB_IMAGEBLIT - select FB select FRAMEBUFFER_CONSOLE if !EMBEDDED select FB_BACKLIGHT if DRM_NOUVEAU_BACKLIGHT select ACPI_VIDEO if ACPI + select VIDEO_OUTPUT_CONTROL if ACPI help Choose this option for open-source nVidia support.
drivers/gpu/drm/Kconfig +1 -1
@@ -22,7 +22,7 @@ menuconfig DRM config DRM_KMS_HELPER tristate depends on DRM - select FB + depends on FB select FRAMEBUFFER_CONSOLE if !EMBEDDED help FB and CRTC helpers for KMS drivers.
Quoted 2 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell <[email protected]>…
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
In an i386 allmodconfig build, compilation of arch/x86/kernel/early_printk_mrst.c is emitting a call to __this_fixmap_does_not_exist().
Quoted 9 lines · Andrew Morton
Quoted 2 lines · On Wed, 13 Oct 2010 15:45:22 +1100 Stephen Rothwell <[email protected]>…
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gitIn an i386 allmodconfig build, compilation of
arch/x86/kernel/early_printk_mrst.cis emitting a call to__this_fixmap_does_not_exist().
Will look at it. Do you happen to have toolchain versions?
-hpa
Quoted 4 lines · On Wed, 13 Oct 2010 17:41:08 -0700 "H. Peter Anvin" <[email protected]> wrote:
Quoted 3 lines · Andrew Morton
On Wed, 13 Oct 2010 15:45:22 +1100
Stephen Rothwell <[email protected]> wrote:
Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gitIn an i386 allmodconfig build, compilation of
arch/x86/kernel/early_printk_mrst.cis emitting a call to__this_fixmap_does_not_exist().Will look at it. Do you happen to have toolchain versions?
gcc-4.1.0. Which is actually an officially banned compiler version:
# if __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ <= 1 # error Your version of gcc miscompiles the __weak directive
lazyass here needs to find a new cross-compiler.
Hi Andrew,
Quoted 17 lines · On Thu, 14 Oct 2010 08:47:40 +0800 Andrew Morton <[email protected]>…
Quoted 4 lines · On Wed, 13 Oct 2010 17:41:08 -0700 "H. Peter Anvin" <[email protected]> wrote:
Quoted 3 lines · Andrew Morton
On Wed, 13 Oct 2010 15:45:22 +1100
Stephen Rothwell <[email protected]> wrote:Quoted 9 lines
Quoted 6 lines
Quoted 2 lines
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.gitIn an i386 allmodconfig build, compilation of
arch/x86/kernel/early_printk_mrst.cis emitting a call to__this_fixmap_does_not_exist().Will look at it. Do you happen to have toolchain versions?
Quoted 6 lines
gcc-4.1.0. Which is actually an officially banned compiler version:
# if __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ <= 1 # error Your version of gcc miscompiles the __weak directivelazyass here needs to find a new cross-compiler.
I just compiled with allmodconfig on X86_32 with gcc 4.4.3 (ubuntu 4.4.3-4ubuntu5) and X86_64 with gcc 4.4.4 (Debian 4.4.4-1), haven't see the error yet.
Thanks,
Feng
Quoted 6 lines · Andrew Morton
gcc-4.1.0. Which is actually an officially banned compiler version:
# if __GNUC_MINOR__ == 1 && __GNUC_PATCHLEVEL__ <= 1 # error Your version of gcc miscompiles the __weak directivelazyass here needs to find a new cross-compiler.
*cough*
http://kernel.org/pub/tools/crosstool/files/bin/
If there are problems let me know.
Yours Tony