ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
- davem has set up a mm-commits mailing list so people can review things
which are added to or removed from the -mm tree. Do
echo subscribe mm-commits | mail [email protected]
- x86_64 architecture update from Andi.
- Everything up to and including `spurious-interrupt-fix.patch' is planned
for 2.6.12 merging. Plus a few other things in there.
- Another DVB subsystem update
Changes since 2.6.12-rc4-mm1:
-sis900-must-select-mii.patch
-move_vma-comment.patch
-remove-drivers-net-skfp-lnkstatc.patch
Merged
+mm-acct-accounting-fix.patch
VM beancounting fix
+x86_64-reduce-nmi-watchdog-stack-usage.patch
+x86_64-readd-missing-tests-in-entrys.patch
+x86_64-add-a-guard-page-at-the-end-of-the-47bit-address.patch
+x86_64-fix-defaults-for-physical-core-id-in.patch
+x86_64-increase-number-of-io-apics.patch
+x86_64-dont-look-up-struct-page-pointer-of-physical.patch
+x86_64-update-tsc-sync-algorithm.patch
+x86_64-remove-x86_apicid-field.patch
+x86_64-dont-print-the-internal-k8c-flag-in.patch
+x86_64-remove-unique-apic-io-apic-id-check.patch
+x86_64-add-pmtimer-support.patch
+x86_64-check-if-ptrace-rip-is-canonical.patch
+x86_64-fix-canonical-checking-for-segment-registers-in.patch
+x86_64-when-checking-vmalloc-mappings-dont-use.patch
+x86_64-fix-oem-hpet-check.patch
+x86_64-make-vsyscallc-compile-without-config_sysctl.patch
+x86_64-collected-nmi-watchdog-fixes.patch
+x86_64-collected-nmi-watchdog-fixes-warning-fix.patch
+x86_64-dont-assume-bsp-has-id-0-in-new-smp-bootup.patch
+x86_64-update-defconfig.patch
x86_64 update
+mm-nommuc-try-to-fix-__vmalloc.patch
nommu build fix
+drivers-input-keyboard-atkbdc-fix-off-by-one-errors.patch
input driver bounds fixes
+s390-dasd-set-online-failure.patch
s/390 driver fix
+swapout-oops-fix.patch
swapout fix
+packet-driver-ioctl-fix.patch
+packet-driver-ioctl-fix-fix.patch
packet driver fix
+crypto-fix-null-encryption-compression.patch
crypto fix
+cdrw-dvd-packet-writing-data-corruption-fix.patch
Fix rare data corruption in packet-writing driver
+spurious-interrupt-fix.patch
Fix spurious interrupt on ia64
-gregkh-01-driver-gregkh-driver-001_driver-pm-diag-update.patch
-gregkh-01-driver-gregkh-driver-002_driver-name-const-01.patch
-gregkh-01-driver-gregkh-driver-003_driver-name-const-02.patch
-gregkh-01-driver-gregkh-driver-004_driver-name-const-03.patch
-gregkh-01-driver-gregkh-driver-005_driver-name-const-04.patch
-gregkh-01-driver-gregkh-driver-006_driver-name-const-05.patch
-gregkh-01-driver-gregkh-driver-007_driver-name-const-06.patch
-gregkh-01-driver-gregkh-driver-008_sysfs-show_store_eio-01.patch
-gregkh-01-driver-gregkh-driver-009_sysfs-show_store_eio-02.patch
-gregkh-01-driver-gregkh-driver-010_sysfs-show_store_eio-03.patch
-gregkh-01-driver-gregkh-driver-011_sysfs-show_store_eio-04.patch
-gregkh-01-driver-gregkh-driver-012_sysfs-show_store_eio-05.patch
-gregkh-01-driver-gregkh-driver-013_class-01-core.patch
-gregkh-01-driver-gregkh-driver-014_class-02-tty.patch
-gregkh-01-driver-gregkh-driver-015_class-03-input.patch
-gregkh-01-driver-gregkh-driver-016_class-04-usb.patch
-gregkh-01-driver-gregkh-driver-017_class-05-sound.patch
-gregkh-01-driver-gregkh-driver-018_class-06-block.patch
-gregkh-01-driver-gregkh-driver-019_class-07-char.patch
-gregkh-01-driver-gregkh-driver-020_class-08-ieee1394.patch
-gregkh-01-driver-gregkh-driver-021_class-09-scsi.patch
-gregkh-01-driver-gregkh-driver-022_class-10-arch.patch
-gregkh-01-driver-gregkh-driver-023_class-11-drivers.patch
-gregkh-01-driver-gregkh-driver-024_class-11-drivers-usb-fix.patch
-gregkh-01-driver-gregkh-driver-025_class-12-the_rest.patch
-gregkh-01-driver-gregkh-driver-026_class-13-kerneldoc.patch
-gregkh-01-driver-gregkh-driver-027_class-14-no_more_class_simple.patch
-gregkh-01-driver-gregkh-driver-028_fix-make-mandocs-after-class_simple-removal.patch
-gregkh-01-driver-gregkh-driver-029_klist-01.patch
-gregkh-01-driver-gregkh-driver-030_klist-02.patch
-gregkh-01-driver-gregkh-driver-031_klist-03.patch
-gregkh-01-driver-gregkh-driver-032_klist-04.patch
-gregkh-01-driver-gregkh-driver-033_klist-05.patch
-gregkh-01-driver-gregkh-driver-034_klist-06.patch
-gregkh-01-driver-gregkh-driver-035_klist-07.patch
-gregkh-01-driver-gregkh-driver-036_klist-08.patch
-gregkh-01-driver-gregkh-driver-037_klist-09.patch
-gregkh-01-driver-gregkh-driver-038_klist-10.patch
-gregkh-01-driver-gregkh-driver-039_klist-11.patch
-gregkh-01-driver-gregkh-driver-040_klist-12.patch
-gregkh-01-driver-gregkh-driver-041_klist-13.patch
-gregkh-01-driver-gregkh-driver-042_klist-14.patch
-gregkh-01-driver-gregkh-driver-043_klist-15.patch
-gregkh-01-driver-gregkh-driver-044_klist-16.patch
-gregkh-01-driver-gregkh-driver-045_klist-17.patch
-gregkh-01-driver-gregkh-driver-046_klist-18.patch
-gregkh-01-driver-gregkh-driver-047_klist-scsi-01.patch
-gregkh-01-driver-gregkh-driver-048_klist-scsi-02.patch
-gregkh-01-driver-gregkh-driver-049_klist-20.patch
-gregkh-01-driver-gregkh-driver-050_klist-21.patch
-gregkh-01-driver-gregkh-driver-051_klist-22.patch
-gregkh-01-driver-gregkh-driver-052_klist-23.patch
-gregkh-01-driver-gregkh-driver-053_klist-ieee1394.patch
-gregkh-01-driver-gregkh-driver-054_klist-pcie.patch
-gregkh-01-driver-gregkh-driver-055_klist-24.patch
-gregkh-01-driver-gregkh-driver-056_klist-25.patch
-gregkh-01-driver-gregkh-driver-057_klist-26.patch
-gregkh-01-driver-gregkh-driver-058_klist-usb_node_attached_fix.patch
-gregkh-01-driver-gregkh-driver-059_klist-sn_fix.patch
-gregkh-01-driver-gregkh-driver-060_klist-driver_detach_fixes.patch
-gregkh-01-driver-gregkh-driver-061_klist-usbcore-dont_call_device_release_driver_recursivly.patch
-gregkh-01-driver-gregkh-driver-062_driver-create-unregister_node.patch
-gregkh-01-driver-gregkh-driver-063_attr_void.patch
+gregkh-driver-driver-pm-diag-update.patch
+gregkh-driver-driver-remove-detach_state.patch
+gregkh-driver-driver-name-const-01.patch
+gregkh-driver-driver-name-const-02.patch
+gregkh-driver-driver-name-const-03.patch
+gregkh-driver-driver-name-const-04.patch
+gregkh-driver-driver-name-const-05.patch
+gregkh-driver-driver-name-const-06.patch
+gregkh-driver-sysfs-show_store_eio-01.patch
+gregkh-driver-sysfs-show_store_eio-02.patch
+gregkh-driver-sysfs-show_store_eio-03.patch
+gregkh-driver-sysfs-show_store_eio-04.patch
+gregkh-driver-sysfs-show_store_eio-05.patch
+gregkh-driver-class-01-core.patch
+gregkh-driver-class-02-tty.patch
+gregkh-driver-class-03-input.patch
+gregkh-driver-class-04-usb.patch
+gregkh-driver-class-05-sound.patch
+gregkh-driver-class-06-block.patch
+gregkh-driver-class-07-char.patch
+gregkh-driver-class-08-ieee1394.patch
+gregkh-driver-class-09-scsi.patch
+gregkh-driver-class-10-arch.patch
+gregkh-driver-class-11-drivers.patch
+gregkh-driver-class-11-drivers-usb-fix.patch
+gregkh-driver-class-12-the_rest.patch
+gregkh-driver-class-13-kerneldoc.patch
+gregkh-driver-class-14-no_more_class_simple.patch
+gregkh-driver-fix-make-mandocs-after-class_simple-removal.patch
+gregkh-driver-klist-01.patch
+gregkh-driver-klist-02.patch
+gregkh-driver-klist-03.patch
+gregkh-driver-klist-04.patch
+gregkh-driver-klist-05.patch
+gregkh-driver-klist-06.patch
+gregkh-driver-klist-07.patch
+gregkh-driver-klist-08.patch
+gregkh-driver-klist-09.patch
+gregkh-driver-klist-10.patch
+gregkh-driver-klist-11.patch
+gregkh-driver-klist-12.patch
+gregkh-driver-klist-13.patch
+gregkh-driver-klist-14.patch
+gregkh-driver-klist-15.patch
+gregkh-driver-klist-16.patch
+gregkh-driver-klist-17.patch
+gregkh-driver-klist-18.patch
+gregkh-driver-klist-scsi-01.patch
+gregkh-driver-klist-scsi-02.patch
+gregkh-driver-klist-20.patch
+gregkh-driver-klist-21.patch
+gregkh-driver-klist-22.patch
+gregkh-driver-klist-23.patch
+gregkh-driver-klist-ieee1394.patch
+gregkh-driver-klist-pcie.patch
+gregkh-driver-klist-24.patch
+gregkh-driver-klist-25.patch
+gregkh-driver-klist-26.patch
+gregkh-driver-klist-usb_node_attached_fix.patch
+gregkh-driver-klist-sn_fix.patch
+gregkh-driver-klist-driver_detach_fixes.patch
+gregkh-driver-klist-usbcore-dont_call_device_release_driver_recursivly.patch
+gregkh-driver-driver-create-unregister_node.patch
+gregkh-driver-attr_void.patch
Greg's patches got renamed again. We're now using stable naming.
-gregkh-02-i2c-gregkh-i2c-001_i2c-ali1563.patch
-gregkh-02-i2c-gregkh-i2c-002_i2c-address_range_removal.patch
-gregkh-02-i2c-gregkh-i2c-003_i2c-address_merge_video.patch
-gregkh-02-i2c-gregkh-i2c-004_w1-ds18xx_sensors.patch
-gregkh-02-i2c-gregkh-i2c-005_w1-new_rom_family.patch
-gregkh-02-i2c-gregkh-i2c-006_i2c-rtc8564_duplicate_include.patch
-gregkh-02-i2c-gregkh-i2c-007_i2c-vid_h.patch
-gregkh-02-i2c-gregkh-i2c-008_i2c-atxp1.patch
-gregkh-02-i2c-gregkh-i2c-009_i2c-atxp1-cleanup.patch
-gregkh-02-i2c-gregkh-i2c-010_i2c-ds1337-01.patch
-gregkh-02-i2c-gregkh-i2c-011_i2c-ds1337-02.patch
-gregkh-02-i2c-gregkh-i2c-012_i2c-ds1337-03.patch
-gregkh-02-i2c-gregkh-i2c-013_i2c-ds1337_make_time_format_consistent.patch
-gregkh-02-i2c-gregkh-i2c-014_i2c-ds1337_i2c_transfer_check.patch
-gregkh-02-i2c-gregkh-i2c-015_i2c-ds1337_search_by_bus_number.patch
-gregkh-02-i2c-gregkh-i2c-016_i2c-ds1337-config-update.patch
-gregkh-02-i2c-gregkh-i2c-017_i2c-config_cleanup-01.patch
-gregkh-02-i2c-gregkh-i2c-018_i2c-config_cleanup-02.patch
-gregkh-02-i2c-gregkh-i2c-019_i2c-adm9240.patch
-gregkh-02-i2c-gregkh-i2c-020_i2c-w83627ehf.patch
-gregkh-02-i2c-gregkh-i2c-021_i2c-w83627ehf-cleanup.patch
-gregkh-02-i2c-gregkh-i2c-022_i2c-smsc47m1.patch
-gregkh-02-i2c-gregkh-i2c-023_i2c-spelling_fixes.patch
-gregkh-02-i2c-gregkh-i2c-024_i2c-mpc-share_interrupt.patch
-gregkh-02-i2c-gregkh-i2c-025_i2c-remove_redundancy_from_i2c_core.patch
-gregkh-02-i2c-gregkh-i2c-026_i2c-remove_delay_h_from_via686a.patch
+gregkh-i2c-i2c-ali1563.patch
+gregkh-i2c-i2c-address_range_removal.patch
+gregkh-i2c-i2c-address_merge_video.patch
+gregkh-i2c-w1-ds18xx_sensors.patch
+gregkh-i2c-w1-new_rom_family.patch
+gregkh-i2c-i2c-rtc8564_duplicate_include.patch
+gregkh-i2c-i2c-vid_h.patch
+gregkh-i2c-i2c-atxp1.patch
+gregkh-i2c-i2c-atxp1-cleanup.patch
+gregkh-i2c-i2c-ds1337-01.patch
+gregkh-i2c-i2c-ds1337-02.patch
+gregkh-i2c-i2c-ds1337-03.patch
+gregkh-i2c-i2c-ds1337_make_time_format_consistent.patch
+gregkh-i2c-i2c-ds1337_i2c_transfer_check.patch
+gregkh-i2c-i2c-ds1337_search_by_bus_number.patch
+gregkh-i2c-i2c-ds1337-config-update.patch
+gregkh-i2c-i2c-ds1337-export-ds1337_do_command.patch
+gregkh-i2c-i2c-config_cleanup-01.patch
+gregkh-i2c-i2c-config_cleanup-02.patch
+gregkh-i2c-i2c-adm9240.patch
+gregkh-i2c-i2c-w83627ehf.patch
+gregkh-i2c-i2c-w83627ehf-cleanup.patch
+gregkh-i2c-i2c-smsc47m1.patch
+gregkh-i2c-i2c-spelling_fixes.patch
+gregkh-i2c-i2c-mpc-share_interrupt.patch
+gregkh-i2c-i2c-remove_redundancy_from_i2c_core.patch
+gregkh-i2c-i2c-remove_delay_h_from_via686a.patch
+gregkh-i2c-i2c-w83627hf-fan-divisor-fix.patch
+gregkh-i2c-i2c-rename-cpu0_vid.patch
Ditto.
+print-kbd-and-aux-irqs-correctly.patch
Fix IRQ repotring printks
+git-jfs.patch
JFS development tree
+git-libata.patch
libata (SATA) development tree
-bk-netdev.patch
Dropped
+git-netdev-8139cp.patch
+git-netdev-8139too-iomap.patch
+git-netdev-amd8111.patch
+git-netdev-e100.patch
+git-netdev-e1000.patch
+git-netdev-forcedeth.patch
+git-netdev-iff-running.patch
+git-netdev-ixgb.patch
+git-netdev-janitor.patch
+git-netdev-orinoco.patch
+git-netdev-ppp.patch
+git-netdev-r8169.patch
+git-netdev-register-netdev.patch
+git-netdev-remove-drivers.patch
+git-netdev-sis900.patch
+git-netdev-skge.patch
+git-netdev-smc91x-eeprom.patch
+git-netdev-starfire.patch
Jeff's netdev trees (mainly network device drivers)
+#git-netdev-wifi.patch
This isn't included because it's busted.
-gregkh-03-pci-gregkh-pci-001_pci-hotplug-shpc-power-fix.patch
-gregkh-03-pci-gregkh-pci-002_pci-pciehp-downstream-port-fix.patch
-gregkh-03-pci-gregkh-pci-003_pci-cpci-update.patch
-gregkh-03-pci-gregkh-pci-004_pci-remove-pci_visit_dev.patch
-gregkh-03-pci-gregkh-pci-005_pci-pci-transparent-bridge-handling-improvements-pci-core.patch
-gregkh-03-pci-gregkh-pci-006_pci-pirq_table_addr-out-of-range.patch
-gregkh-03-pci-gregkh-pci-007_pci-get_device-01.patch
-gregkh-03-pci-gregkh-pci-008_pci-get_device-02.patch
-gregkh-03-pci-gregkh-pci-009_pci-acpiphp-02.patch
-gregkh-03-pci-gregkh-pci-010_pci-acpiphp-03.patch
-gregkh-03-pci-gregkh-pci-011_pci-acpiphp-04.patch
-gregkh-03-pci-gregkh-pci-012_pci-acpiphp-05.patch
-gregkh-03-pci-gregkh-pci-013_pci-acpiphp-06.patch
-gregkh-03-pci-gregkh-pci-014_pci-acpiphp-07.patch
-gregkh-03-pci-gregkh-pci-015_pci-acpiphp-08.patch
-gregkh-03-pci-gregkh-pci-016_pci-acpiphp-09.patch
-gregkh-03-pci-gregkh-pci-017_pci-acpiphp-10.patch
-gregkh-03-pci-gregkh-pci-018_pci-acpiphp-11.patch
-gregkh-03-pci-gregkh-pci-019_pci-acpiphp-12.patch
-gregkh-03-pci-gregkh-pci-020_pci-acpiphp-13.patch
-gregkh-03-pci-gregkh-pci-021_pci-acpiphp-14.patch
-gregkh-03-pci-gregkh-pci-022_pci-acpiphp-15.patch
-gregkh-03-pci-gregkh-pci-023_pci-acpiphp-16.patch
-gregkh-03-pci-gregkh-pci-024_pci-acpiphp-17.patch
-gregkh-03-pci-gregkh-pci-025_pci-acpiphp-18.patch
-gregkh-03-pci-gregkh-pci-026_pci-acpiphp-19.patch
-gregkh-03-pci-gregkh-pci-027_pci-acpiphp-20.patch
-gregkh-03-pci-gregkh-pci-028_pci-serverworks-gc-quirk.patch
+gregkh-pci-pci-hotplug-shpc-power-fix.patch
+gregkh-pci-pci-pciehp-downstream-port-fix.patch
+gregkh-pci-pci-cpci-update.patch
+gregkh-pci-pci-remove-pci_visit_dev.patch
+gregkh-pci-pci-modalias-sysfs.patch
+gregkh-pci-pci-modalias-hotplug.patch
+gregkh-pci-pci-pci-transparent-bridge-handling-improvements-pci-core.patch
+gregkh-pci-pci-pirq_table_addr-out-of-range.patch
+gregkh-pci-pci-get_device-01.patch
+gregkh-pci-pci-get_device-02.patch
+gregkh-pci-pci-acpiphp-02.patch
+gregkh-pci-pci-acpiphp-03.patch
+gregkh-pci-pci-acpiphp-04.patch
+gregkh-pci-pci-acpiphp-05.patch
+gregkh-pci-pci-acpiphp-06.patch
+gregkh-pci-pci-acpiphp-07.patch
+gregkh-pci-pci-acpiphp-08.patch
+gregkh-pci-pci-acpiphp-09.patch
+gregkh-pci-pci-acpiphp-10.patch
+gregkh-pci-pci-acpiphp-11.patch
+gregkh-pci-pci-acpiphp-12.patch
+gregkh-pci-pci-acpiphp-13.patch
+gregkh-pci-pci-acpiphp-14.patch
+gregkh-pci-pci-acpiphp-15.patch
+gregkh-pci-pci-acpiphp-16.patch
+gregkh-pci-pci-acpiphp-17.patch
+gregkh-pci-pci-acpiphp-18.patch
+gregkh-pci-pci-acpiphp-19.patch
+gregkh-pci-pci-acpiphp-20.patch
+gregkh-pci-pci-serverworks-gc-quirk.patch
Greg's PCI devel tree
+add-scsi-changer-driver.patch
+add-scsi-changer-driver-gregkh-driver-fix.patch
Bring back the SCSI changer driver
-gregkh-04-USB-gregkh-usb-001_usb-usbnet-fixes.patch
-gregkh-04-USB-gregkh-usb-002_usb-ehci-suspend-stop-timer.patch
-gregkh-04-USB-gregkh-usb-003_usb-g_file_storage_min.patch
-gregkh-04-USB-gregkh-usb-004_usb-g_file_storage_stall.patch
-gregkh-04-USB-gregkh-usb-005_usb-omap_udc_update.patch
-gregkh-04-USB-gregkh-usb-006_usb-isp116x-hcd-add.patch
-gregkh-04-USB-gregkh-usb-007_usb-isp116x-hcd-fix.patch
-gregkh-04-USB-gregkh-usb-008_usb-turn-a-user-mode-driver-error-into-a-hard-error.patch
-gregkh-04-USB-gregkh-usb-009_usb-uhci-01.patch
-gregkh-04-USB-gregkh-usb-010_usb-uhci-02.patch
-gregkh-04-USB-gregkh-usb-011_usb-uhci-03.patch
-gregkh-04-USB-gregkh-usb-012_usb-uhci-04.patch
-gregkh-04-USB-gregkh-usb-013_usb-uhci-05.patch
-gregkh-04-USB-gregkh-usb-014_usb-uhci-06.patch
-gregkh-04-USB-gregkh-usb-015_usb-uhci-07.patch
-gregkh-04-USB-gregkh-usb-016_usb-uhci-08.patch
-gregkh-04-USB-gregkh-usb-017_usb-root_hub_irq.patch
-gregkh-04-USB-gregkh-usb-018_usb-cdc_acm.patch
-gregkh-04-USB-gregkh-usb-019_usb-usbtest.patch
-gregkh-04-USB-gregkh-usb-020_usb-ohci_reboot_notifier.patch
-gregkh-04-USB-gregkh-usb-021_usb_serial_status.patch
-gregkh-04-USB-gregkh-usb-022_usb-zd1201_pm.patch
-gregkh-04-USB-gregkh-usb-023_usb-zd1201_pm-02.patch
-gregkh-04-USB-gregkh-usb-024_usb-remove_hub_set_power_budget.patch
-gregkh-04-USB-gregkh-usb-025_usb-device_pointer.patch
-gregkh-04-USB-gregkh-usb-026_usb-hcd_fix_for_remove_hub_set_power_budget.patch
-gregkh-04-USB-gregkh-usb-027_usb-usbcore_usb_add_hcd.patch
-gregkh-04-USB-gregkh-usb-028_usb-hcds_no_more_register_root_hub.patch
-gregkh-04-USB-gregkh-usb-029_usb-ub_multi_lun.patch
-gregkh-04-USB-gregkh-usb-030_usb-rndis_cleanups.patch
-gregkh-04-USB-gregkh-usb-031_usb-ethernet_gadget_cleanups.patch
-gregkh-04-USB-gregkh-usb-032_usb-omap_udc_cleanups.patch
-gregkh-04-USB-gregkh-usb-033_usb-dummy_hcd-otg.patch
-gregkh-04-USB-gregkh-usb-034_usb-dummy_hcd-FEAT.patch
-gregkh-04-USB-gregkh-usb-035_usb-dummy_hcd-pdevs.patch
-gregkh-04-USB-gregkh-usb-036_usb-dummy_hcd-centralize-link.patch
-gregkh-04-USB-gregkh-usb-037_usb-dummy_hcd-root-hub_no-polling.patch
-gregkh-04-USB-gregkh-usb-038_usb-remove_pwc_changelog.patch
-gregkh-04-USB-gregkh-usb-039_usb-add-new-wacom-device-to-usb-hid-core-list.patch
-gregkh-04-USB-gregkh-usb-040_usb-urb_documentation.patch
-gregkh-04-USB-gregkh-usb-041_usb-idmouse_update.patch
-gregkh-04-USB-gregkh-usb-042_usb-gadget-kconfig.patch
-gregkh-04-USB-gregkh-usb-043_usb-gadget-setup-api-change.patch
-gregkh-04-USB-gregkh-usb-044_usb-gadget-setup-api-change-net2280.patch
-gregkh-04-USB-gregkh-usb-045_usb-gadget-setup-api-change-goku_udc.patch
-gregkh-04-USB-gregkh-usb-046_usb-gadget-pxa2xx_udc-updates.patch
-gregkh-04-USB-gregkh-usb-047_usb-ehci-minor-updates.patch
-gregkh-04-USB-gregkh-usb-048_usb-earthmate-hid-blacklist.patch
+gregkh-usb-usb-usbnet-fixes.patch
+gregkh-usb-usb-ehci-suspend-stop-timer.patch
+gregkh-usb-usb-modalias-sysfs.patch
+gregkh-usb-usb-cypress_m8-add-lt-20-support.patch
+gregkh-usb-usb-g_file_storage_min.patch
+gregkh-usb-usb-g_file_storage_stall.patch
+gregkh-usb-usb-omap_udc_update.patch
+gregkh-usb-usb-isp116x-hcd-add.patch
+gregkh-usb-usb-isp116x-hcd-fix.patch
+gregkh-usb-usb-turn-a-user-mode-driver-error-into-a-hard-error.patch
+gregkh-usb-usb-uhci-01.patch
+gregkh-usb-usb-uhci-02.patch
+gregkh-usb-usb-uhci-03.patch
+gregkh-usb-usb-uhci-04.patch
+gregkh-usb-usb-uhci-05.patch
+gregkh-usb-usb-uhci-06.patch
+gregkh-usb-usb-uhci-07.patch
+gregkh-usb-usb-uhci-08.patch
+gregkh-usb-usb-root_hub_irq.patch
+gregkh-usb-usb-cdc_acm.patch
+gregkh-usb-usb-usbtest.patch
+gregkh-usb-usb-ohci_reboot_notifier.patch
+gregkh-usb-usb_serial_status.patch
+gregkh-usb-usb-zd1201_pm.patch
+gregkh-usb-usb-zd1201_pm-02.patch
+gregkh-usb-usb-remove_hub_set_power_budget.patch
+gregkh-usb-usb-device_pointer.patch
+gregkh-usb-usb-hcd_fix_for_remove_hub_set_power_budget.patch
+gregkh-usb-usb-usbcore_usb_add_hcd.patch
+gregkh-usb-usb-hcds_no_more_register_root_hub.patch
+gregkh-usb-usb-ub_multi_lun.patch
+gregkh-usb-usb-rndis_cleanups.patch
+gregkh-usb-usb-ethernet_gadget_cleanups.patch
+gregkh-usb-usb-omap_udc_cleanups.patch
+gregkh-usb-usb-dummy_hcd-otg.patch
+gregkh-usb-usb-dummy_hcd-FEAT.patch
+gregkh-usb-usb-dummy_hcd-pdevs.patch
+gregkh-usb-usb-dummy_hcd-centralize-link.patch
+gregkh-usb-usb-dummy_hcd-root-hub_no-polling.patch
+gregkh-usb-usb-remove_pwc_changelog.patch
+gregkh-usb-usb-add-new-wacom-device-to-usb-hid-core-list.patch
+gregkh-usb-usb-urb_documentation.patch
+gregkh-usb-usb-idmouse_update.patch
+gregkh-usb-usb-gadget-kconfig.patch
+gregkh-usb-usb-gadget-setup-api-change.patch
+gregkh-usb-usb-gadget-setup-api-change-net2280.patch
+gregkh-usb-usb-gadget-setup-api-change-goku_udc.patch
+gregkh-usb-usb-gadget-pxa2xx_udc-updates.patch
+gregkh-usb-usb-ehci-minor-updates.patch
+gregkh-usb-usb-earthmate-hid-blacklist.patch
+gregkh-usb-usb-usbatm-1.patch
+gregkh-usb-usb-usbatm-2.patch
+gregkh-usb-usb-usbatm-3.patch
+gregkh-usb-usb-usbatm-4.patch
+gregkh-usb-usb-usbatm-5.patch
+gregkh-usb-usb-dummy_hcd-sparse-cleanups.patch
+gregkh-usb-usb-dummy_hcd-suspend-and-resume.patch
Greg's USB tree
-zd1201-build-fix.patch
Seems that this reappeared in one of Jeff's trees, but I think it's wrong.
+mystery-ide-fix.patch
Undocumented but apparently terribly important IDE fix.
+sparsemem-memory-model-fix.patch
+sparsemem-memory-model-for-i386-fix.patch
Kick the sparsemem stuff into shape.
-fix-ieee80211_crypt_-selects.patch
Merged, or fixed by other means, or simply broken.
+fix-atm-build-with-o=.patch
+drivers-net-hamradio-baycom_eppc-cleanups.patch
+ppp_mppe-add-ppp-mppe-encryption-module.patch
+dm9000-network-driver-bugfix.patch
+documentation-networking-dmfetxt-make-documentation-nicer.patch
Networking fixes
+ppc64-abolish-ioremap_mm.patch
ppc64 cleanup
+mips-add-resource-management-to-pmu.patch
MIPS power management addition
+platform-smis-and-their-interferance-with-tsc-based-delay-calibration-fix.patch
Fix platform-smis-and-their-interferance-with-tsc-based-delay-calibration.patch
+adjust-i386-watchdog-tick-calculation.patch
+allow-early-printk-to-use-more-than-25-lines.patch
x86 fixes
-remove-unique-apic-io-apic-id-check.patch
-x86_64-dont-assume-bp-to-be-the-first-one-in-madt-mps.patch
Drop a couple of x86_64 patches which are obsoleted by Andi's patches.
+optimise-storage-of-read-mostly-variables-x86_64-fix-fix.patch
Yet another fix to optimise-storage-of-read-mostly-variables.patch
+x86_64-eliminate-duplicate-rdpmc-definition.patch
x86_64 fixlet
+dmi-move-acpi-boot-quirk.patch
+dmi-move-acpi-sleep-quirk.patch
+dmi-remove-central-blacklist.patch
+dmi-code-spring-cleanup.patch
DMI code cleanups and fixes
+alpha-osf_sys-use-helper-functions-to-convert-between-tv-and-jiffies.patch
Alpha code cleanup
+kprobes-function-return-probes-fix-4.patch
+kprobes-arch_supports_kretprobes-cleanup.patch
Fix kprobes-function-return-probes.patch even more
-fix-pci-mmap-on-ppc-and-ppc64-fix.patch
Folded into fix-pci-mmap-on-ppc-and-ppc64.patch
+dont-force-o_largefile-for-32-bit-processes-on-ia64-2612-rc3.patch
ia64 x86 emulation fix
+ide-floppy-adjustments.patch
ide-floppy build fix
+adjust-per_cpu-definition-in-non-smp-case.patch
per_cpu() build fix
+apply-quotation-handling-to-makefilebuild.patch
makefile robustness
+pcmcia-ds-handle-any-error-code.patch
pcmcia fix
+mempool-only-init-waitqueue-in-slow-path.patch
mempool microoptimisation
+seccomp-disable-tsc-for-seccomp-enabled-tasks.patch
Disable TSC when using secure computing. Adds code to switch_to() :(
+kill-asm-ioctl32h.patch
cleanup
+profilec-schedule-parsing-fix.patch
Fix __setup parser
+factor-out-common-code-in-sys_fsync-sys_fdatasync.patch
Code consolidation
+improve-cd-dvd-packet-driver-write-performance.patch
Speed up the packet writing driver
+tpm-add-debugging-output.patch
tpm driver work
+connector-export-initialization-flag.patch
connector namespace fix
+dvb-b2c2-flexcop-driver-refactoring-part-1-drop-old-b2c2-usb-stuff.patch
+dvb-b2c2-flexcop-driver-refactoring-part-2-add-modular-flexcop-driver.patch
+dvb-flexcop-fix-usb-transfer-handling.patch
+dvb-flexcop-add-acknowledgements.patch
+dvb-flexcop-fix-mac-address-reading.patch
+dvb-flexcop-fixed-interrupt-sharing.patch
+dvb-flexcop-use-hw-pid-filter.patch
+dvb-flexcop-fix-module-refcount-handling.patch
+dvb-flexcop-readme-update.patch
+dvb-flexcop-i2c-read-fixes.patch
+dvb-flexcop-diseqc-fix.patch
dvd subsystem updates
+numa-aware-slab-allocator-v3.patch
+numa-aware-slab-allocator-v2-tidy.patch
+numa-aware-slab-allocator-v3-cleanup.patch
+ppc64-numa-nodes-hack.patch
NUMA-aware slab allocator (a bit busted on ppc64)
+v4l-saa7134-mark-little-endian-ptr.patch
+video_cx88_dvb-must-select-dvb_cx22702.patch
+fix-for-cx88-cardsc-for-dvico-fusionhdtv-3-gold-q.patch
v4l subsystem updates
+kexec-x86_64-optimise-storage-of-read-mostly-variables-x86_64-fix.patch
Fix kexec for the `optimise-storage-of-read-mostly-variables' patch
-reiser4-sb_sync_inodes-cleanup.patch
This was broken.
+intelfbdrv-naming-fix.patch
+fbdev-iomove-removal.patch
+pm3fb-typo-fix.patch
fbdev updates
+md-cause-md-raid1-to-repack-working-devices-when-number-of-drives-is-changed.patch
+md-make-sure-recovery-happens-when-add_new_disk-is-used-for-hot_add.patch
RAID updates
+kernel-power-swsuspc-make-a-variable-static.patch
+kernel-modulec-make-a-function-static.patch
+fs-reiserfs-streec-make-max_key-static.patch
+make-umount_tree-static.patch
+scsi-make-code-static.patch
Make some things static
+drivers-char-ip2-cleanups.patch
+drivers-cdrom-cm206c-cleanups.patch
+drivers-isdn-hisax-possible-cleanups.patch
Little fixes
-remove-exports-for-oem-modules.patch
Dropped: the code which needs these exports has been merged.
number of patches in -mm: 1166
number of changesets in external trees: 223
number of patches in -mm only: 1158
total patches: 1381
All 1166 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/patch-list
On Mon, May 16, 2005 at 02:13:02AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
If you wish, you could add the three git trees I have on m.k.o into
the mix - ~rmk/linux-2.6-*.git
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
Andrew Morton <[email protected]> wrote:
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
include/acpi/achware.h:159: warning: `struct acpi_gpe_block_info' declared inside parameter list
include/acpi/achware.h:159: warning: `struct acpi_gpe_xrupt_info' declared inside parameter list
include/acpi/achware.h:159: warning: type defaults to `int' in declaration of `acpi_hw_enable_runtime_gpe_block'
include/acpi/achware.h:159: warning: data definition has no type or storage class
make[2]: *** [arch/x86_64/kernel/time.o] Error 1
make[1]: *** [arch/x86_64/kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.12-rc4-mm2'
make: *** [stamp-build] Error 2
Debian-amd64
Kernel config: http://newsgate.newsserver.nl/kernel/dotconfig-2.6.12-rc4-mm2
Danny
--
The foundation of evil is made up of lies and marketing - UF2004
On Monday 16 May 2005 14:50, Danny ter Haar wrote:
> Andrew Morton <[email protected]> wrote:
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
> include/acpi/achware.h:159: warning: `struct acpi_gpe_block_info' declared inside parameter list
> include/acpi/achware.h:159: warning: `struct acpi_gpe_xrupt_info' declared inside parameter list
> include/acpi/achware.h:159: warning: type defaults to `int' in declaration of `acpi_hw_enable_runtime_gpe_block'
> include/acpi/achware.h:159: warning: data definition has no type or storage class
> make[2]: *** [arch/x86_64/kernel/time.o] Error 1
Does this help?
Signed-off-by: Alexey Dobriyan <[email protected]>
--- linux-2.6.12-rc4-mm2/include/acpi/achware.h 2005-05-16 14:24:02.000000000 +0400
+++ linux-2.6.12-rc4-mm2-acpi/include/acpi/achware.h 2005-05-16 15:11:39.000000000 +0400
@@ -44,6 +44,14 @@
#ifndef __ACHWARE_H__
#define __ACHWARE_H__
+#include <linux/types.h>
+#include <acpi/actypes.h>
+
+struct acpi_bit_register_info;
+struct acpi_generic_address;
+struct acpi_gpe_event_info;
+struct acpi_gpe_xrupt_info;
+struct acpi_gpe_block_info;
/* PM Timer ticks per second (HZ) */
For reference, the oops below still occurs with 2.6.12-rc4-mm2. I've noticed
that "/sbin/init: error while loading shared libraries: /sbin/init: Cannot
allocate version reference table: Cannot allocate Memory" appears on the
console just before the "Kernel panic".
2.6.12-rc4, 2.6.12-rc3-mm2 and 2.6.12-rc3-mm3 all work with the same root
filesystem which suggests this is a kernel issue of some sort.
Richard Purdie:
> 2.6.12-rc4-mm1 on a Sharp Zaurus (arm pxa255) results in:
>
> VFS: Mounted root (jffs2 filesystem) readonly.
> Freeing init memory: 76K
> Kernel panic - not syncing: Attempted to kill init!
> <3>BUG: soft lockup detected on CPU#0!
>
> Pid: 1, comm: init
> CPU: 0
> PC is at __delay+0x0/0xc
> LR is at panic+0x108/0x130
> pc : [<c00f71ac>] lr : [<c0037140>] Not tainted
> sp : c0301f4c ip : c0301f4c fp : c0301f58
> r10: 4001d000 r9 : c0300000 r8 : 00007f00
> r7 : c0300000 r6 : c027a3e8 r5 : c027a3e4 r4 : 0000240b
> r3 : 60000013 r2 : 000003ca r1 : 00000000 r0 : 00017133
> Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment user
> Control: 397F Table: A1CB0000 DAC: 00000015
> [<c0059c90>] (softlockup_tick+0x0/0xa0) from [<c0021020>]
> (timer_tick+0xb4/0xf8)
> r5 = C0300000 r4 = C0301F04
> [<c0020f6c>] (timer_tick+0x0/0xf8) from [<c00277e0>]
> (pxa_timer_interrupt+0x48/0xa8)
> r6 = C0301F04 r5 = C0300000 r4 = F2A00000
> [<c0027798>] (pxa_timer_interrupt+0x0/0xa8) from [<c001cbc4>]
> (__do_irq+0x6c/0xc4)
> r8 = C0301F04 r7 = 00000000 r6 = 00000000 r5 = C0300000
> r4 = C0230374
> [<c001cb58>] (__do_irq+0x0/0xc4) from [<c001ce48>]
> (do_level_IRQ+0x68/0xb8)
> [<c001cde0>] (do_level_IRQ+0x0/0xb8) from [<c001ceec>]
> (asm_do_IRQ+0x54/0x160)
> r6 = 04000000 r5 = F2D00000 r4 = FFFFFFFF
> [<c001ce98>] (asm_do_IRQ+0x0/0x160) from [<c001ba14>]
> (__irq_svc+0x34/0x74)
> [<c0037038>] (panic+0x0/0x130) from [<c003a22c>] (do_exit+0x7c8/0xda4)
> r3 = 00000001 r2 = C02E8E40 r1 = C02E8D60 r0 = C02004C0
> [<c0039a64>] (do_exit+0x0/0xda4) from [<c003a900>]
> (do_group_exit+0xc0/0x104)
> [<c003a840>] (do_group_exit+0x0/0x104) from [<c001be20>]
> (ret_fast_syscall+0x0/0x2c)
> r5 = 00000000 r4 = 0000002F
>
> There was an extremely long pause after it printed "Kernel panic ..."
> before it printed the traceback.
Alexey Dobriyan <[email protected]> wrote:
>Does this help?
>--- linux-2.6.12-rc4-mm2/include/acpi/achware.h 2005-05-16 14:24:02.000000000 +0400
>+++ linux-2.6.12-rc4-mm2-acpi/include/acpi/achware.h 2005-05-16 15:11:39.000000000 +0400
[SNIP]
[PATCH APPLIED]
Nope, (unfortunatly)
Complete error is at:
http://newsgate.newsserver.nl/kernel/2.6.12-rc4-mm2-error-out.txt
Danny
--
The foundation of evil is made up of lies and marketing - UF2004
On Monday 16 May 2005 15:38, Danny ter Haar wrote:
> Alexey Dobriyan <[email protected]> wrote:
> >Does this help?
> >--- linux-2.6.12-rc4-mm2/include/acpi/achware.h
> >+++ linux-2.6.12-rc4-mm2-acpi/include/acpi/achware.h
> Nope, (unfortunatly)
Please, try this.
Signed-off-by: Alexey Dobriyan <[email protected]>
--- linux-2.6.12-rc4-mm2/include/acpi/achware.h 2005-05-16 14:24:02.000000000 +0400
+++ linux-2.6.12-rc4-mm2-acpi/include/acpi/achware.h 2005-05-16 16:05:41.000000000 +0400
@@ -44,6 +44,8 @@
#ifndef __ACHWARE_H__
#define __ACHWARE_H__
+struct acpi_gpe_xrupt_info;
+struct acpi_gpe_block_info;
/* PM Timer ticks per second (HZ) */
Andrew Morton a ?crit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
>
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
>
> echo subscribe mm-commits | mail [email protected]
>
> - x86_64 architecture update from Andi.
>
> - Everything up to and including `spurious-interrupt-fix.patch' is planned
> for 2.6.12 merging. Plus a few other things in there.
>
> - Another DVB subsystem update
Hi Andrew,
CONFIG_PPP_MPPE can be enabled without CONFIG_CRYPTO.
This results in this warning when running make modules_install:
if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map 2.6.12-rc4-mm2=LoulousMobile; fi
WARNING:
/lib/modules/2.6.12-rc4-mm2=LoulousMobile/kernel/drivers/net/ppp_mppe.ko
needs unknown symbol crypto_alloc_tfm
WARNING:
/lib/modules/2.6.12-rc4-mm2=LoulousMobile/kernel/drivers/net/ppp_mppe.ko
needs unknown symbol crypto_free_tfm
By the way, looking at drivers/net/ppp_mppe.c, it looks like sha1 and
arc4 are needed at runtime.
The attached patch selects all these when PPP_MPPE is selected.
Signed-off-by: Brice Goglin <[email protected]>
Brice
Alexey Dobriyan <[email protected]> wrote:
>> Alexey Dobriyan <[email protected]> wrote:
>> >Does this help?
>> Nope, (unfortunatly)
>Please, try this.
[Patch #2 applied]
Still not succesful..
Error is at
http://newsgate.newsserver.nl/kernel/2.6.12-rc4-mm2-patch%232-error-out.txt
btw:
newsgate:/usr/src/linux-2.6.12-rc4-mm2# gcc -v
Reading specs from /usr/lib/gcc-lib/x86_64-linux/3.3.6/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--enable-__cxa_atexit --with-system-zlib --enable-nls
--without-included-gettext --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
--disable-multilib x86_64-linux
Thread model: posix
gcc version 3.3.6 (Debian 1:3.3.6-4)
newsgate:/var/www/kernel# ls -lrt
-rw-r--r-- 1 root root 3638 May 16 13:36 2.6.12-rc4-mm2-error-out.txt
-rw-r--r-- 1 root root 5389 May 16 19:07 2.6.12-rc4-mm2-patch#2-error-out.txt
Thanks for your efforts to help me!
Danny
--
The foundation of evil is made up of lies and marketing - UF2004
On Monday 16 May 2005 21:11, Danny ter Haar wrote:
> Alexey Dobriyan <[email protected]> wrote:
> >> Alexey Dobriyan <[email protected]> wrote:
> >> >Does this help?
> >> Nope, (unfortunatly)
> >Please, try this.
>
> [Patch #2 applied]
>
> Still not succesful..
>
> Error is at
> http://newsgate.newsserver.nl/kernel/2.6.12-rc4-mm2-patch%232-error-out.txt
Urgh... ACPI uses catch-all header file.
If this won't work, I'll get a cross-compiler.
--- linux-2.6.12-rc4-mm2/arch/x86_64/kernel/time.c 2005-05-16 21:38:04.000000000 +0400
+++ linux-2.6.12-rc4-mm2-acpi/arch/x86_64/kernel/time.c 2005-05-16 21:38:49.000000000 +0400
@@ -27,7 +27,7 @@
#include <linux/bcd.h>
#include <linux/kallsyms.h>
#include <linux/acpi.h>
-#include <acpi/achware.h> /* for PM timer frequency */
+#include <acpi/acpi.h>
#include <asm/8253pit.h>
#include <asm/pgtable.h>
#include <asm/vsyscall.h>
Comparing 2.6.12-rc4-mm1 to 2.6.12-rc4-mm2 (defconfig)
======================================================
- alpha: broke
AR arch/alpha/lib/lib.a
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
mm/built-in.o(.text+0xe79c):/usr/src/ctest/mm/kernel/mm/slab.c:339: undefined reference to `__bad_size'
mm/built-in.o(.text+0xe7a0):/usr/src/ctest/mm/kernel/mm/slab.c:339: undefined reference to `__bad_size'
make[1]: *** [.tmp_vmlinux1] Error 1
make: *** [_all] Error 2
Details: http://l4x.org/k/?d=3741
- mips: broke
CC mm/mempool.o
CC mm/oom_kill.o
CC mm/fadvise.o
CC mm/page_alloc.o
CC mm/page-writeback.o
CC mm/pdflush.o
CC mm/readahead.o
CC mm/slab.o
mm/slab.c:117:2: #error "Broken Configuration: CONFIG_NUMA not set but MAX_NUMNODES !=1 !!"
make[1]: *** [mm/slab.o] Error 1
make: *** [mm] Error 2
Details: http://l4x.org/k/?d=3753
--
Jan
It seems proc-pid-smaps.patch is guilty for this nommu breakage in -mm:
<-- snip -->
...
LD vmlinux
fs/built-in.o(.text+0x32b08): In function `smaps_open':
/usr/src/ctest/mm/kernel/fs/proc/base.c:560: undefined reference to `_proc_pid_smaps_op'
make[1]: *** [vmlinux] Error 1
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Alexey Dobriyan <[email protected]> wrote:
>Urgh... ACPI uses catch-all header file.
>If this won't work, I'll get a cross-compiler.
take #3
still no luck.
Less output then previous trial.
Danny
PS: need an account so you can compile on the machine in question ?
--
The foundation of evil is made up of lies and marketing - UF2004
Jan Dittmer <[email protected]> wrote:
>
> Comparing 2.6.12-rc4-mm1 to 2.6.12-rc4-mm2 (defconfig)
> ======================================================
>
> - alpha: broke
> AR arch/alpha/lib/lib.a
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> mm/built-in.o(.text+0xe79c):/usr/src/ctest/mm/kernel/mm/slab.c:339: undefined reference to `__bad_size'
> mm/built-in.o(.text+0xe7a0):/usr/src/ctest/mm/kernel/mm/slab.c:339: undefined reference to `__bad_size'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [_all] Error 2
>
argh, I forgot to add the patch to the series file, sorry.
From: Andrew Morton <[email protected]>
This doesn't work (on alpha, at least).
It's not inside __builtin_constant_p() so the compiler cannot be sure that all
the possible sizes have been checked for.
Cc: Christoph Lameter <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---
mm/slab.c | 12 +++++++-----
1 files changed, 7 insertions(+), 5 deletions(-)
diff -puN mm/slab.c~numa-aware-slab-allocator-v3-__bad_size-fix mm/slab.c
--- 25-alpha/mm/slab.c~numa-aware-slab-allocator-v3-__bad_size-fix 2005-05-15 22:25:33.000000000 -0700
+++ 25-alpha-akpm/mm/slab.c 2005-05-15 22:30:10.000000000 -0700
@@ -325,7 +325,8 @@ struct kmem_list3 __initdata initkmem_li
*/
static inline int index_of(const size_t size)
{
- int i = 0;
+ if (__builtin_constant_p(size)) {
+ int i = 0;
#define CACHE(x) \
if (size <=x) \
@@ -334,11 +335,12 @@ static inline int index_of(const size_t
i++;
#include "linux/kmalloc_sizes.h"
#undef CACHE
- {
- extern void __bad_size(void);
- __bad_size();
- return 0;
+ {
+ extern void __bad_size(void);
+ __bad_size();
+ }
}
+ return 0;
}
#define INDEX_AC index_of(sizeof(struct array_cache))
_
>
> - mips: broke
> CC mm/mempool.o
> CC mm/oom_kill.o
> CC mm/fadvise.o
> CC mm/page_alloc.o
> CC mm/page-writeback.o
> CC mm/pdflush.o
> CC mm/readahead.o
> CC mm/slab.o
> mm/slab.c:117:2: #error "Broken Configuration: CONFIG_NUMA not set but MAX_NUMNODES !=1 !!"
> make[1]: *** [mm/slab.o] Error 1
> make: *** [mm] Error 2
>
OK, Christoph is scratching his head over that one.
Andrew Morton a ?crit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
Hi Andrew,
Cardmgr does not automatically start my pcmcia wireless card anymore.
orinoco modules are not loaded at all.
I still can modprobe orinoco_cs to get my wireless to work.
Cardmgr says this when starting:
cardmgr[27367]: no pcmcia driver in /proc/devices
Is this a feature related to the upcoming deprecation of cardctl ?
Am I supposed to use pcmcia-utils ?
Thanks,
Brice
Brice Goglin:
> Cardmgr does not automatically start my pcmcia wireless card anymore.
> orinoco modules are not loaded at all.
> I still can modprobe orinoco_cs to get my wireless to work.
>
> Cardmgr says this when starting:
> cardmgr[27367]: no pcmcia driver in /proc/devices
>
> Is this a feature related to the upcoming deprecation of cardctl ?
> Am I supposed to use pcmcia-utils ?
I also see the above message on the arm pxa zaurus with -mm2. I'm still
using pcmcia-cs rather than pcmcia-utils. pcmcia+cardmgr works fine in -mm1.
I'm also not sure if this is by design or not...
Regards,
Richard
On 5/16/05, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
>
> echo subscribe mm-commits | mail [email protected]
I see patches being added to and removed from -mm tree. Is it
possible to know the reason why they are removed, whether they are
merged upstream or dropped?
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
m?n 2005-05-16 klockan 02:13 -0700 skrev Andrew Morton:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
>
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
>
> echo subscribe mm-commits | mail [email protected]
>
> - x86_64 architecture update from Andi.
>
> - Everything up to and including `spurious-interrupt-fix.patch' is planned
> for 2.6.12 merging. Plus a few other things in there.
>
> - Another DVB subsystem update
>
I need this to be able to compile on x64 without CONFIG_ACPI (yeah it's
probably wrong all the way, but can someone that knows acpi fix it
please?). Tested on i386 & x64 w & w/o CONFIG_ACPI.
Index: kexec/include/linux/acpi.h
===================================================================
--- kexec.orig/include/linux/acpi.h 2005-05-18 22:04:11.000000000 +0200
+++ kexec/include/linux/acpi.h 2005-05-18 22:13:13.000000000 +0200
@@ -25,8 +25,6 @@
#ifndef _LINUX_ACPI_H
#define _LINUX_ACPI_H
-#ifdef CONFIG_ACPI
-
#ifndef _LINUX
#define _LINUX
#endif
@@ -419,6 +417,8 @@
#else /*!CONFIG_ACPI_BOOT*/
+static inline int acpi_boot_init (void) { return 0; }
+static inline int acpi_boot_table_init (void) { return 0; }
#define acpi_mp_config 0
#endif /*!CONFIG_ACPI_BOOT*/
@@ -531,18 +531,4 @@
extern int pnpacpi_disabled;
-#else /* CONFIG_ACPI */
-
-static inline int acpi_boot_init(void)
-{
- return 0;
-}
-
-static inline int acpi_boot_table_init(void)
-{
- return 0;
-}
-
-#endif /* CONFIG_ACPI */
-
#endif /* _LINUX_ACPI_H */
On Tuesday 17 May 2005 5:38 pm, Richard Purdie wrote:
> Brice Goglin:
> > Cardmgr does not automatically start my pcmcia wireless card anymore.
> > orinoco modules are not loaded at all.
> > I still can modprobe orinoco_cs to get my wireless to work.
> >
> > Cardmgr says this when starting:
> > cardmgr[27367]: no pcmcia driver in /proc/devices
> >
> > Is this a feature related to the upcoming deprecation of cardctl ?
> > Am I supposed to use pcmcia-utils ?
>
> I also see the above message on the arm pxa zaurus with -mm2. I'm still
> using pcmcia-cs rather than pcmcia-utils. pcmcia+cardmgr works fine in
> -mm1. I'm also not sure if this is by design or not...
I found the problem. The pcmcia-move-pcmcia-ioctl-to-a-separate-file patch was
corrupted in -mm2 causing this problem. The fix is below.
Richard
--- linux-2.6.11.orig/drivers/pcmcia/ds.c 2005-05-18 23:27:43.000000000 +0100
+++ linux-2.6.11/drivers/pcmcia/ds.c 2005-05-17 17:13:50.000000000 +0100
@@ -1199,6 +1199,9 @@
bus_register(&pcmcia_bus_type);
class_interface_register(&pcmcia_bus_interface);
+
+ pcmcia_setup_ioctl();
+
return 0;
}
fs_initcall(init_pcmcia_bus); /* one level after subsys_initcall so that
@@ -1212,7 +1215,6 @@
class_interface_unregister(&pcmcia_bus_interface);
bus_unregister(&pcmcia_bus_type);
- pcmcia_setup_ioctl();
}
module_exit(exit_pcmcia_bus);
Andrew Morton a ?crit :
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
>
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
>
> echo subscribe mm-commits | mail [email protected]
>
> - x86_64 architecture update from Andi.
>
> - Everything up to and including `spurious-interrupt-fix.patch' is planned
> for 2.6.12 merging. Plus a few other things in there.
>
> - Another DVB subsystem update
Hi Andrew and Dominik,
Since mm2, udev cannot rename my pcmcia wireless interface.
rc4 and rc4-mm1 successfully rename it from eth0 to wifi.
rc4-mm2 only renames the internal interface, not the pcmcia wifi one.
When I insert the card, This line appears in syslog:
udev[9500]: configured rule in '/etc/udev/rules.d/brice.rules[4]'
applied, 'eth0' becomes 'wifi'
But the interface is still called eth0.
Any idea ?
Thanks,
Brice
PS: Richard Purdie's patch (http://lkml.org/lkml/2005/5/18/303) fixed my
previous cardctl breakage, but it doesn't change anything regarding this
bug.
Hi Adrian,
How did you get this error? What is your configuration?
I would like to replicate it.
BR,
Mauricio Lin.
On 5/16/05, Adrian Bunk <[email protected]> wrote:
> It seems proc-pid-smaps.patch is guilty for this nommu breakage in -mm:
>
> <-- snip -->
>
> ...
> LD vmlinux
> fs/built-in.o(.text+0x32b08): In function `smaps_open':
> /usr/src/ctest/mm/kernel/fs/proc/base.c:560: undefined reference to `_proc_pid_smaps_op'
> make[1]: *** [vmlinux] Error 1
>
> <-- snip -->
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
Hi Adrian,
I guess that the code below you have to include in the
fs/proc/task_nommu.c. But I would like to replicate the error you
found and apply the code below to verify if it is correct. So if you
can explain how you got this error I can test the code below. If you
want to test the code below by yourself, let me know about the result
please.
static int show_smap(struct seq_file *m, void *v)
{
return 0;
}
struct seq_operations proc_pid_smaps_op = {
.start = m_start,
.next = m_next,
.stop = m_stop,
.show = show_smap
};
BR,
Mauricio Lin.
On 5/20/05, Mauricio Lin <[email protected]> wrote:
> Hi Adrian,
>
> How did you get this error? What is your configuration?
>
> I would like to replicate it.
>
> BR,
>
> Mauricio Lin.
>
> On 5/16/05, Adrian Bunk <[email protected]> wrote:
> > It seems proc-pid-smaps.patch is guilty for this nommu breakage in -mm:
> >
> > <-- snip -->
> >
> > ...
> > LD vmlinux
> > fs/built-in.o(.text+0x32b08): In function `smaps_open':
> > /usr/src/ctest/mm/kernel/fs/proc/base.c:560: undefined reference to `_proc_pid_smaps_op'
> > make[1]: *** [vmlinux] Error 1
> >
> > <-- snip -->
> >
> > cu
> > Adrian
> >
> > --
> >
> > "Is there not promise of rain?" Ling Tan asked suddenly out
> > of the darkness. There had been need of rain for many days.
> > "Only a promise," Lao Er said.
> > Pearl S. Buck - Dragon Seed
> >
> >
>
On Mon, May 16, 2005 at 02:13:02AM -0700, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
> - davem has set up a mm-commits mailing list so people can review things
> which are added to or removed from the -mm tree. Do
> echo subscribe mm-commits | mail [email protected]
> - x86_64 architecture update from Andi.
> - Everything up to and including `spurious-interrupt-fix.patch' is planned
> for 2.6.12 merging. Plus a few other things in there.
> - Another DVB subsystem update
try_to_unmap_cluster() does:
for (pte = pte_offset_map(pmd, address);
address < end; pte++, address += PAGE_SIZE) {
...
}
pte_unmap(pte);
It may take a little staring to notice, but pte can actually fall off
the end of the pte page in this iteration, which makes life difficult
for kmap_atomic() and the users not expecting it to BUG(). Of course,
we're somewhat lucky in that arithmetic elsewhere in the function
guarantees that at least one iteration is made, lest this force larger
rearrangements to be made. This issue and patch also apply to non-mm
mainline and with trivial adjustments, at least two related kernels.
Discovered during internal testing at Oracle. Sample BUG() message
included along with patch as a MIME attachment.
Signed-off-by: William Irwin <[email protected]>
-- wli
William Lee Irwin III <[email protected]> wrote:
>
> try_to_unmap_cluster() does:
> for (pte = pte_offset_map(pmd, address);
> address < end; pte++, address += PAGE_SIZE) {
> ...
> }
>
> pte_unmap(pte);
>
> It may take a little staring to notice, but pte can actually fall off
> the end of the pte page in this iteration,
That's about the third place we've had this bug. Whoever keeps adding it
really should stop.
Thanks.
William Lee Irwin III <[email protected]> wrote:
>
> --- ./mm/rmap.c.orig 2005-05-20 01:29:14.066467151 -0700
> +++ ./mm/rmap.c 2005-05-20 01:30:06.620649901 -0700
> @@ -694,7 +694,7 @@
> (*mapcount)--;
> }
>
> - pte_unmap(pte);
> + pte_unmap(pte-1);
> out_unlock:
> spin_unlock(&mm->page_table_lock);
> }
I must say that I continue to find this approach a bit queazifying.
After some reading of the code I'd agree that yes, it's not possible for us
to get here with `pte' pointing at the first slot of the pte page, but it's
not 100% obvious and it's possible that someone will come along later and
will change things in try_to_unmap_cluster() which cause this unmap to
suddenly do the wrong thing in rare circumstances.
IOW: I'd sleep better at night if we took a temporary and actually unmapped
the thing which we we got back from pte_offset_map().. Am I being silly?
William Lee Irwin III <[email protected]> wrote:
>> --- ./mm/rmap.c.orig 2005-05-20 01:29:14.066467151 -0700
>> +++ ./mm/rmap.c 2005-05-20 01:30:06.620649901 -0700
[...]
On Mon, May 23, 2005 at 05:14:06PM -0700, Andrew Morton wrote:
> I must say that I continue to find this approach a bit queazifying.
> After some reading of the code I'd agree that yes, it's not possible for us
> to get here with `pte' pointing at the first slot of the pte page, but it's
> not 100% obvious and it's possible that someone will come along later and
> will change things in try_to_unmap_cluster() which cause this unmap to
> suddenly do the wrong thing in rare circumstances.
> IOW: I'd sleep better at night if we took a temporary and actually unmapped
> the thing which we we got back from pte_offset_map().. Am I being silly?
Not at all. I merely attempt to minimize diffsize by default. An
alternative implementation follows (changelog etc. to be taken
from the prior patch) in case it saves the time (however short) needed
to write it yourself.
-- wli
Index: mm2-2.6.12-rc4/mm/rmap.c
===================================================================
--- mm2-2.6.12-rc4.orig/mm/rmap.c 2005-05-20 01:44:18.000000000 -0700
+++ mm2-2.6.12-rc4/mm/rmap.c 2005-05-23 19:13:29.000000000 -0700
@@ -626,7 +626,7 @@
pgd_t *pgd;
pud_t *pud;
pmd_t *pmd;
- pte_t *pte;
+ pte_t *pte, *original_pte;
pte_t pteval;
struct page *page;
unsigned long address;
@@ -658,7 +658,7 @@
if (!pmd_present(*pmd))
goto out_unlock;
- for (pte = pte_offset_map(pmd, address);
+ for (original_pte = pte = pte_offset_map(pmd, address);
address < end; pte++, address += PAGE_SIZE) {
if (!pte_present(*pte))
@@ -694,7 +694,7 @@
(*mapcount)--;
}
- pte_unmap(pte);
+ pte_unmap(original_pte);
out_unlock:
spin_unlock(&mm->page_table_lock);
}
On Mon, 23 May 2005, William Lee Irwin III wrote:
> On Mon, May 23, 2005 at 05:14:06PM -0700, Andrew Morton wrote:
> > I must say that I continue to find this approach a bit queazifying.
> > After some reading of the code I'd agree that yes, it's not possible for us
> > to get here with `pte' pointing at the first slot of the pte page, but it's
> > not 100% obvious and it's possible that someone will come along later and
> > will change things in try_to_unmap_cluster() which cause this unmap to
> > suddenly do the wrong thing in rare circumstances.
> > IOW: I'd sleep better at night if we took a temporary and actually unmapped
> > the thing which we we got back from pte_offset_map().. Am I being silly?
There's a similar argument for queasiness in all the other (8 or more)
instances of the idiom. I think we originally adopted (and I furthered)
this pte_unmap(pte - 1) idiom because in the majority of architecture's
configurations pte_unmap does nothing at all, so we resented assigning
a pointless variable in some critical loops.
> Not at all. I merely attempt to minimize diffsize by default. An
> alternative implementation follows (changelog etc. to be taken
> from the prior patch) in case it saves the time (however short) needed
> to write it yourself.
Either of wli's patches is fine with me. There are several levels on
which try_to_unmap_cluster is harder to understand than the others,
and no good reason to resist the variable assignment.
We could rewrite pte_unmap to avoid the issue completely, since its
job is to unmap (or pretend to unmap) KM_PTE0's pte if the address
is in the fixmap area: but changing it to tolerate an off-by-one
address gives a queasy feeling too.
Thanks,
Hugh
Hugh Dickins wrote:
> On Mon, 23 May 2005, William Lee Irwin III wrote:
>
>>On Mon, May 23, 2005 at 05:14:06PM -0700, Andrew Morton wrote:
>>
>>>I must say that I continue to find this approach a bit queazifying.
>>>After some reading of the code I'd agree that yes, it's not possible for us
>>>to get here with `pte' pointing at the first slot of the pte page, but it's
>>>not 100% obvious and it's possible that someone will come along later and
>>>will change things in try_to_unmap_cluster() which cause this unmap to
>>>suddenly do the wrong thing in rare circumstances.
>>>IOW: I'd sleep better at night if we took a temporary and actually unmapped
>>>the thing which we we got back from pte_offset_map().. Am I being silly?
>
>
> There's a similar argument for queasiness in all the other (8 or more)
> instances of the idiom. I think we originally adopted (and I furthered)
> this pte_unmap(pte - 1) idiom because in the majority of architecture's
> configurations pte_unmap does nothing at all, so we resented assigning
> a pointless variable in some critical loops.
>
Still, the compiler should be able to eliminate that extra register
as well as it can eliminate the intermediate (pte - 1) result (that
is to say, I hope perfectly in this day and age).
It may be more of an issue with architectures that actually *do* do
something in pte_unmap, in which case perhaps you increase the
register pressure over the critical loop? I guess we can just laugh
at them.
>
>>Not at all. I merely attempt to minimize diffsize by default. An
>>alternative implementation follows (changelog etc. to be taken
>>from the prior patch) in case it saves the time (however short) needed
>>to write it yourself.
>
>
> Either of wli's patches is fine with me. There are several levels on
> which try_to_unmap_cluster is harder to understand than the others,
> and no good reason to resist the variable assignment.
>
> We could rewrite pte_unmap to avoid the issue completely, since its
> job is to unmap (or pretend to unmap) KM_PTE0's pte if the address
> is in the fixmap area: but changing it to tolerate an off-by-one
> address gives a queasy feeling too.
>
Looks like no architecture (other than maybe frv?) even uses the
kvaddr argument to kunmap_atomic unless HIGHMEM_DEBUG/DEBUG_HIGHMEM
is enabled. If you stored that info elsewhere, you wouldn't even
need to pass the argument in.
But hmm... I don't see anyone getting motivated enough to rewrite the
debug code over this issue :)
--
SUSE Labs, Novell Inc.
On Mon, 16 May 2005 02:13:02 -0700, Andrew Morton <[email protected]> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
>
>
Hi...
I have a (stupid, I suppose) problem with framebuffer console.
I have builtin VESAFB in this kernel, so:
werewolf:/boot# grep _FB config-2.6.21-jam09 | grep =y
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_VESA=y
werewolf:/boot# grep CONSO config-2.6.21-jam09
# CONFIG_NETCONSOLE is not set
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
I put this line in grub's menu.lst:
kernel /boot/vmlinuz video=vesafb:mtrr,ywrap vga=0x31A ro root=/dev/sdc1
(tried both with hex and decimal).
but grub keeps telling me it can't set that video mode, and I have no
/dev/fb0 device to try with fbset. I have a '29 fb' line in /proc/devices.
Any ideas about why the device is missing ? udev is 113...
I have followed al the info I could get (linux/Documentation/fb/, Google ;) )
and all say that what I'm doing should work. What am I doing wrong ?
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2008.0 (Cooker) for i586
Linux 2.6.21-jam09 (gcc 4.1.2 20070302 (4.1.2-1mdv2007.1)) SMP PREEMPT
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On Wed, 27 Jun 2007 02:35:27 +0200 "J.A. Magall?n" <[email protected]> wrote:
> On Mon, 16 May 2005 02:13:02 -0700, Andrew Morton <[email protected]> wrote:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc4/2.6.12-rc4-mm2/
> >
> >
>
> Hi...
>
> I have a (stupid, I suppose) problem with framebuffer console.
> I have builtin VESAFB in this kernel, so:
>
> werewolf:/boot# grep _FB config-2.6.21-jam09 | grep =y
> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_DEFERRED_IO=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_VESA=y
> werewolf:/boot# grep CONSO config-2.6.21-jam09
> # CONFIG_NETCONSOLE is not set
> CONFIG_VT_CONSOLE=y
> CONFIG_HW_CONSOLE=y
> # CONFIG_VT_HW_CONSOLE_BINDING is not set
> CONFIG_VGA_CONSOLE=y
> CONFIG_DUMMY_CONSOLE=y
> CONFIG_FRAMEBUFFER_CONSOLE=y
> # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>
> I put this line in grub's menu.lst:
>
> kernel /boot/vmlinuz video=vesafb:mtrr,ywrap vga=0x31A ro root=/dev/sdc1
>
> (tried both with hex and decimal).
>
> but grub keeps telling me it can't set that video mode, and I have no
> /dev/fb0 device to try with fbset. I have a '29 fb' line in /proc/devices.
>
> Any ideas about why the device is missing ? udev is 113...
> I have followed al the info I could get (linux/Documentation/fb/, Google ;) )
> and all say that what I'm doing should work. What am I doing wrong ?
>
Methinks that'll be git-newsetup changes?
Hi J.A. :)
* J.A. Magall?n <[email protected]> dixit:
> kernel /boot/vmlinuz video=vesafb:mtrr,ywrap vga=0x31A ro root=/dev/sdc1
>
> (tried both with hex and decimal).
Try "vga=0x031A". I vaguely remember I had a similar problem and
IIRC that's how I solved it. Anyway, you can always try vga=ask and try
to enter the number by hand, just to see which modes work.
Ra?l N??ez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
Andrew Morton wrote:
>>
>> I have a (stupid, I suppose) problem with framebuffer console.
>> I have builtin VESAFB in this kernel, so:
>>
>> werewolf:/boot# grep _FB config-2.6.21-jam09 | grep =y
^^^^^^
Is this actually the -mm kernel? And if so, does it work in earlier
kernels?
-hpa