2.6.12-mm2
Subsystems (6)
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/
- A reminder that there is a vger mailing list for tracking patches which are added to -mm. Do
`echo subscribe mm-commits | mail [email protected]'
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
- Big arch/cris update.
Changes since 2.6.12-mm1:
-x86_64-task_size-fixes-for-compatibility-mode-processes.patch
-smp_processor_id-cleanup.patch
-smp_processor_id-cleanup-fix.patch
-git-alsa-fix.patch
-git-alsa-usbaudio-fix.patch
-gregkh-driver-driver-device_attr-08-fix.patch
-gregkh-i2c-i2c-ds1374-01-fix.patch
-toshiba-driver-cleanup.patch
-i8k-pass-through-lindent.patch
-i8k-use-standard-dmi-interface.patch
-i8k-convert-to-seqfile.patch
-i8k-initialization-code-cleanup-formatting.patch
-i8k-add-new-bios-signatures.patch
-biarch-compiler-support-for-i386.patch
-use-cross_compileinstallkernel-in-arch-boot-installsh.patch -ipvs-add-and-reorder-bh-locks-after-moving-to-keventd.patch -drivers-net-chelsio-cxgb2-use-the-dma_3264bit_mask-constants.patch
-tcp-fastroute-stats-remove.patch
-tcp-no-congestion.patch
-tcp-no-throttle.patch
-tcp-bigger-backlog.patch
-tcp-tcp_super_tso_v3.patch
-tcp-tcp_infra.patch
-tcp-tcp_bic.patch
-tcp-tcp_westwood.patch
-tcp-hstcp.patch
-tcp-hybla.patch
-tcp-vegas.patch
-tcp-h-tcp.patch
-tcp-scaleable_tcp.patch
-gregkh-pci-pci-driver-device_attr-fixup.patch
-vmscan-notice-slab-shrinking.patch
-madvise-do-not-split-the-maps.patch
-madvise-merge-the-maps.patch
-remove-non-discontig-use-of-pgdat-node_mem_map.patch -resubmit-sparsemem-base-early_pfn_to_nid-works-before-sparse-is-initialized.patch -resubmit-sparsemem-base-simple-numa-remap-space-allocator.patch -resubmit-sparsemem-base-reorganize-page-flags-bit-operations.patch -resubmit-sparsemem-base-teach-discontig-about-sparse-ranges.patch -create-mm-kconfig-for-arch-independent-memory-options.patch
-make-each-arch-use-mm-kconfig.patch
-make-each-arch-use-mm-kconfig-fix.patch
-update-all-defconfigs-for-arch_discontigmem_enable.patch -introduce-new-kconfig-option-for-numa-or-discontig.patch -sparsemem-fix-minor-defaults-issue-in-mm-kconfig.patch
-mm-kconfig-kill-unused-arch_flatmem_disable.patch
-mm-kconfig-hide-memory-model-selection-menu.patch
-mm-kconfig-give-discontig-more-help-text.patch
-ppc64-kconfig-memory-models.patch
-generify-early_pfn_to_nid.patch
-generify-memory-present.patch
-sparsemem-memory-model.patch
-sparsemem-memory-model-fix.patch
-sparsemem-memory-model-fix-3.patch
-sparsemem-memory-model-fix-4.patch
-sparsemem-memory-model-fix-5.patch
-sparsemem-memory-model-fix-6.patch
-sparsemem-memory-model-section-numbers-unsigned-long.patch
-sparsemem-memory-model-for-i386.patch
-sparsemem-memory-model-for-i386-fix.patch
-sparsemem-swiss-cheese-numa-layouts.patch
-sparsemem-hotplug-base.patch
-sparsemem-hotplug-base-fix.patch
-sparsemem-hotplug-base-abstract-section-number-to-section-mapping.patch
-ppc64-add-early_pfn_to_nid.patch
-ppc64-add-memory-present.patch
-ppc64-sparsemem-memory-model.patch
-ppc64-sparsemem-memory-model-fix.patch
-ppc64-sparsemem-memory-model-fix-2.patch
-remove-direct-ref-to-contig_page_data-for-x86-64.patch
-add-x86-64-kconfig-options-for-sparsemem.patch -reorganize-x86-64-numa-and-discontigmem-config-options.patch -add-x86-64-specific-support-for-sparsemem.patch
-add-x86-64-specific-support-for-sparsemem-tidy.patch
-add-page_state-info-to-show_mem.patch
-add-page_state-info-to-show_mem-warning-fixes.patch
-mm-add-proc-zoneinfo.patch
-vm-add-may_swap-flag-to-scan_control.patch
-vm-early-zone-reclaim.patch
-vm-early-zone-reclaim-tidy.patch
-vm-add-__gfp_noreclaim.patch
-vm-rate-limit-early-reclaim.patch
-hugepage-consolidation.patch
-hugepage-consolidation-fix.patch
-hugepage-consolidation-fix-fix.patch
-hugepage-consolidation-ia64-fix.patch
-node-local-per-cpu-pages.patch
-node-local-per-cpu-pages-tidy.patch
-node-local-per-cpu-pages-tidy-2.patch
-node-local-per-cpu-pages-tidy-2-fix.patch
-avoiding-mmap-fragmentation.patch
-avoiding-mmap-fragmentation-tidy.patch
-avoiding-mmap-fragmentation-fix.patch
-avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes.patch -avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes-vs-x86_64-task_size-fixes-for-compatibility-mode-processes.patch -avoiding-mmap-fragmentation-revert-unneeded-64-bit-changes-vs-x86_64-task_size-fixes-for-compatibility-mode-processes-fix.patch -avoiding-mmap-fragmentation-fix-2.patch
-avoiding-mmap-fragmentation-fix-3.patch
-mmap-topdown-fix-for-large-stack-limit-large-allocation.patch -#avoiding-mmap-fragmentation-clean-rev.patch
-mm-remove-pg_highmem.patch
-mm-remove-pg_highmem-tidy.patch
-vm-try_to_free_pages-unused-argument.patch
-__mod_page_state-pass-unsigned-long-instead-of-unsigned.patch -__read_page_state-pass-unsigned-long-instead-of-unsigned.patch
-add-oom-debug.patch
-periodically-drain-non-local-pagesets.patch
-periodically-drain-non-local-pagesets-fix.patch
-reduce-size-of-huge-boot-per_cpu_pageset.patch
-ia64-uncached-alloc.patch
-sn2-xpc-build-patches.patch
-shmem-restore-superblock-info.patch
-mbind-fix-verify_pages-pte_page.patch
-mbind-check_range-use-standard-ptwalk.patch
-dup_mmap-update-comment-on-new-vma.patch
-bad_page-clear-reclaim-and-slab.patch
-rme96xx-fix-pagereserved-range.patch
-get_user_pages-kill-get_page_map.patch
-do_wp_page-cannot-share-file-page.patch
-can_share_swap_page-use-page_mapcount.patch
-msync-check-pte-dirty-earlier.patch
-kill-stray-newline.patch
-netfilter-debug-locking-fix.patch
-tulip-fixes-for-uli5261.patch
-3c509-device-support.patch
-ppp_mppe-add-ppp-mppe-encryption-module-kconfig-fix.patch
-dm9000-network-driver-bugfix.patch
-x25-selective-sub-address-matching-with.patch
-x25-selective-sub-address-matching-with-fix.patch
-x25-fast-select-with-no-restriction-on.patch
-sunzilog-warning-fixes.patch
-ppp-handle-misaligned-accesses.patch -3c59x-remove-superfluous-vortex_debug-test-from-boomerang_start_xmit.patch -kbuild-display-compile-version.patch
-vfs-memory-leak-in-do_kern_mount.patch
-selinux-memory-leak-in-selinux_sb_copy_data.patch -ppc32-added-support-for-new-mpc8548-family-of-powerquicc.patch -ppc32-added-preliminary-support-for-the-mpc8548-cds-board.patch -ppc32-removed-dependency-on-config_cpm2-for-building.patch -ppc32-converted-mpc10x-bridge-to-use-platform.patch
-cpm_uart-route-scc2-pins-for-the-stx-gp3-board.patch
-ppc32-fix-config_task_size-handling-on-40x.patch -ppc32-add-support-for-mpc8245-8250-serial-ports-on-sandpoint.patch -ppc32-remove-orphaned-ppc4xx_kgdbc.patch
-ppc32-added-support-for-all-mpc8548-internal-interrupts.patch -ppc32-clean-up-num_tlbcams-usage-for-freescale-book-e-ppcs.patch -ppc32-factor-out-common-exception-code-into-macros-for.patch -ppc32-remove-some-unnecessary-includes-of-promh.patch -ppc32-dont-recursively-crash-in-die-on-chrp-prep-machines.patch -ppc32-kill-embedded-systemmap-use-kallsyms.patch
-ppc64-abolish-ioremap_mm.patch
-ppc64-quieten-rtas-printks.patch -ppc64-override-command-line-as-ld-cc-variables-when-adding-m64-and-co-for-biarch-compilers.patch -ppc64-use-cpu_has_feature-macro.patch
-ppc64-iseries-remove-iseries_proch.patch
-ppc64-iseries-header-file-white-space-cleanups.patch -ppc64-iseries-more-header-file-white-space-cleanups.patch -ppc64-iseries-obvious-code-simplifications.patch
-ppc64-iseries-remove-lpardatah.patch
-ppc64-iseries-eliminate-some-unused-inline-functions.patch
-ppc64-iseries-remove-hvcallcfgh.patch
-ppc64-iseries-cleanup-itlpqueueh.patch
-ppc64-iseries-tidy-up-some-includes-and-hvcallh.patch
-ppc64-iseries-misc-header-cleanups.patch
-ppc64-iseries-remove-iseries_pci_resetc.patch
-ppc64-iseries-iommuh-cleanups.patch
-ppc64-iseries-iseries_vpdinfoc-cleanups.patch
-ppc64-iseries-iseries_pcih-cleanups.patch
-ppc64-iseries-remove-ioretry-from-iseries_device_node.patch -ppc64-iseries-remove-some-more-members-of.patch
-ppc64-iseries-irq-simple-cleanups.patch
-ppc64-iseries-remove-xmpcilpeventc.patch
-ppc64-iseries-tidy-up-irq-code-after-merge.patch
-ppc64-iseries-allow-build-with-no-pci.patch
-ppc64-tidy-up-vio-devices-fake-parent.patch
-mips-add-vr41xx-gpio-support.patch
-mips-add-vr41xx-gpio-support-fix.patch -#sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch -platform-smis-and-their-interferance-with-tsc-based-delay-calibration.patch -platform-smis-and-their-interferance-with-tsc-based-delay-calibration-fix.patch -m32r-build-fix-for-asm-m32r-topologyh.patch
-ppc64-pcibus_to_node-fix.patch
-x86-x86_64-pcibus_to_node.patch
-x86-x86_64-pcibus_to_node-fix.patch
-fix-pcibus_to_node-for-x86_64.patch
-allow-pcibus_to_node-to-return-undetermined.patch -numa-aware-block-device-control-structure-allocation.patch -numa-aware-block-device-control-structure-allocation-tidy.patch
-i386-never-block-forced-sigsegv.patch
-do-not-enforce-unique-io_apic_id-check-for-xapic-systems-i386.patch -adjust-i386-watchdog-tick-calculation.patch
-allow-early-printk-to-use-more-than-25-lines.patch
-i386-selectable-frequency-of-the-timer-interrupt.patch -i386-selectable-frequency-of-the-timer-interrupt-fix.patch -ia64-selectable-timer-interrupt-frequency.patch
-x86-avoid-wasting-irqs-for-pci-devices.patch
-via-82c586b-irq-routing-fix.patch
-x86-include-asm-uaccessh-in-asm-checksumh.patch
-x86-remove-i386_ksymsc-almost.patch
-x86-cpu_khz-type-fix.patch
-x86_64-i8259c-iso99-structure-initialization.patch -x86_64-fix-hpet-for-systems-that-dont-support-legacy.patch -optimise-storage-of-read-mostly-variables.patch
-optimise-storage-of-read-mostly-variables-fix.patch -optimise-storage-of-read-mostly-variables-x86_64-fix.patch -optimise-storage-of-read-mostly-variables-x86_64-fix-fix.patch -optimise-storage-of-read-mostly-variables-x86_64-fix-fix-fix.patch -move-some-more-structures-into-mostly_readonly-and-readonly.patch
-x86_64-never-block-forced-sigsegv.patch
-x86_64-eliminate-duplicate-rdpmc-definition.patch
-x86_64-avoid-wasting-irqs.patch
-dmi-move-acpi-boot-quirk.patch
-dmi-move-acpi-sleep-quirk.patch
-dmi-move-acpi-sleep-quirk-fix.patch
-dmi-remove-central-blacklist.patch
-dmi-code-spring-cleanup.patch
-xen-x86-add-macro-for-debugreg.patch
-xen-x86-use-new-macro-for-debugreg.patch
-xen-x86-rename-usermode-macro.patch
-xen-x86-rename-usermode-macro-fix.patch
-xen-x86-use-more-usermode-macro.patch
-xen-x86_64-add-macro-for-debugreg.patch
-xen-x86_64-use-more-usermode-macro.patch
-ptrace_h8300-condition-bugfix.patch
-arm-irqs_disabled-type-fix.patch
-ioc4-core-driver-rewrite.patch
-ioc4-config-split.patch
-ioc4-pci-bus-speed-detection.patch
-variable-overflow-after-hundreds-round-of-hotplug-cpu.patch
-i386-cpu-hotplug-updated-for-mm.patch
-i386-cpu-hotplug-updated-for-mm-smp_processor_id-cleanup-fix.patch -i386-dont-use-ipi-broadcast-when-using-cpu-hotplug.patch
-sep-initializing-rework.patch
-sep-initializing-rework-fix.patch
-sep-initializing-rework-cleanup.patch
-i386-hold-call_lock-when-updating-cpu_online_map.patch
-sibling-map-initializing-rework.patch
-sibling-map-initializing-rework-smp_processor_id-cleanup-fix.patch
-init-call-cleanup.patch
-cpu-state-clean-after-hot-remove.patch -cpu-state-clean-after-hot-remove-smp_processor_id-cleanup-fix.patch -cpu-state-clean-after-hot-remove-set-cpu_state-for-cpu-hotplug.patch -cpu-state-clean-after-hot-remove-fix.patch
-cpu-state-clean-after-hot-remove-fix-2.patch
-physical-cpu-hot-add.patch
-physical-cpu-hot-add-fix.patch
-suspend-resume-smp-support.patch
-suspend-resume-smp-support-fix.patch
-suspend-resume-smp-support-fix-2.patch
-suspend-resume-smp-support-fix-3.patch
-swsusp-documentation-updates.patch
-swsusp-kill-config_pm_disk.patch
-s-t-ram-load-gdt-the-right-way.patch
-acpi-fix-video-docs.patch
-properly-stop-devices-before-poweroff.patch
-properly-stop-devices-before-poweroff-fix.patch
-swsusp-kill-unneccessary-does_collide_order.patch
-swsusp-cleanup-whitespace.patch
-swsusp-fix-nr_copy_pages.patch
-swsusp-clean-assembly-parts.patch
-cpu-hotplug-printk-fix.patch
-suspend-pci-power-managment-reference-implementation.patch
-swsusp-only-allow-it-when-it-makes-sense.patch
-update-video-after-suspend-documentation.patch
-x86_64-change-init-sections-for-cpu-hotplug-support.patch -x86_64-change-init-sections-for-cpu-hotplug-support-fix.patch
-x86_64-cpu-hotplug-support.patch
-x86_64-cpu-hotplug-support-fix.patch
-x86_64-cpu-hotplug-sibling-map-cleanup.patch -x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe.patch -x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe-fix.patch -x86_64-dont-use-broadcast-shortcut-to-make-it-cpu-hotplug-safe-fix-set-cpu_state-for-cpu-hotplug.patch -x86_64-provide-ability-to-choose-using-shortcuts-for-ipi-in-flat-mode.patch -set-cpu_state-for-cpu-hotplug-ia64.patch
-m32r-support-m3a-2170mappi-iii-platform.patch
-m32r-support-m3a-2170mappi-iii-platform-fix.patch
-m32r-support-m3a-2170mappi-iii-platform-fix-2.patch
-m32r-update-setup_xxxxxc.patch
-m32r-update-m32r_cfc-to-support-mappi-iii.patch
-m32r-update-m32r_cfc-to-support-mappi-iii-fix.patch
-m32r-cleanup-arch-m32r-mm-extablec.patch
-m32r-remove-include-asm-m32r-m32102perih.patch
-m32r-update-defconfig-files.patch
-m32r-use-asm-generic-div64h.patch
-uml-add-and-use-generic-hw_controller_type-release.patch -uml-complete-hw_controller_type-release-conversion.patch -uml-make-hw_controller_type-release-exist-only-for-archs-needing-it.patch -uml-link-tt-mode-against-nptl.patch
-s390-cio-max-channels-checks.patch
-s390-cio-documentation.patch
-s390-ifdefs-in-compat_ioctls.patch
-s390-kernel-stack-overflow-panic.patch
-s390-cmm-sender-parameter-visibility.patch
-s390-memory-detection-32gb.patch
-s390-pending-interrupt-after-ipl-from-reader.patch
-mtrr-size-and-base-debug.patch
-blk-use-find_first_zero_bit-in-blk_queue_start_tag.patch -blk-remove-blk_queue_tag-real_max_depth-optimization.patch
-blk-remove-blk_tags_per_longmask.patch
-blk-cleanup-generic-tag-support-error-messages.patch
-blk-no-memory-barrier.patch
-blk-branch-hints.patch
-blk-unplug-later.patch
-keys-discard-key-spinlock-and-use-rcu-for-key-payload.patch -keys-discard-key-spinlock-and-use-rcu-for-key-payload-try-4.patch -keys-pass-session-keyring-to-call_usermodehelper.patch -keys-pass-session-keyring-to-call_usermodehelper-fix.patch -keys-use-rcu-to-manage-session-keyring-pointer.patch -keys-make-request-key-create-an-authorisation-key.patch -keys-make-request-key-create-an-authorisation-key-fix.patch
-ecryptfs-export-user-key-type.patch
-timers-fixes-improvements.patch
-timers-fixes-improvements-smp_processor_id-fix.patch
-timers-fixes-improvements-fix.patch
-timers-fixes-improvements-smp_processor_id-cleanup-fix.patch -timers-fix-__mod_timer-vs-__run_timers-deadlock.patch -timers-fix-__mod_timer-vs-__run_timers-deadlock-tidy.patch
-timers-comments-update.patch
-kernel-timerc-remove-a-goto-construct.patch
-timers-introduce-try_to_del_timer_sync.patch
-posix-timers-use-try_to_del_timer_sync.patch
-fix-for-prune_icache-forced-final-iput-races.patch
-create-a-kstrdup-library-function.patch
-create-a-kstrdup-library-function-fixes.patch
-create-a-kstrdup-library-function-fix-include-slab.patch
-create-a-kstrdup-library-function-ppc-fix.patch
-kstrdup-convert-a-few-existing-implementations.patch -con_consdev-bit-not-set-correctly-on-last-console.patch
-as-limit-queue-depth.patch
-as-limit-queue-depth-fix.patch
-generate-hotplug-events-for-cpu-online.patch
-optimise-loop-driver-a-bit.patch
-optimise-loop-driver-a-bit-tidy.patch
-streamline-preempt_count-type-across-archs.patch -preempt_count-is-int-remove-cast-and-dont-assign-to.patch
-add-check-to-proc-devices-read-routines.patch
-rpc-kick-off-socket-connect-operations-faster.patch -remove-register_ioctl32_conversion-and-unregister_ioctl32_conversion.patch -remove-duplicate-get_dentry-functions-in-various-places.patch
-avoid-recursive-oopses.patch
-quota-consolidate-code-surrounding-vfs_quota_on_mount.patch -quota-sanitize-dentry-handling-in-vfs_quota_on_mount.patch
-kprobes-function-return-probes.patch
-kprobes-function-return-probes-fix.patch
-kprobes-function-return-probes-fix-2.patch
-kprobes-function-return-probes-fix-3.patch
-kprobes-function-return-probes-fix-4.patch -kprobes-move-aggregate-probe-handlers-and-few-return-probe-routines-to-static.patch -kprobes-arch_supports_kretprobes-cleanup.patch
-kprobes-function-return-probes-fix-5.patch
-x86_64-specific-function-return-probes.patch
-move-kprobe-arming-into-arch-specific-code.patch -kprobes-moves-lock-unlock-to-non-arch-kprobe_flush_task.patch
-kprobes-ia64-kdebug-die-notification.patch
-kprobes-ia64-kdebug-die-notification-fix.patch
-kprobes-ia64-arch-specific-handling-of-kprobes.patch -kprobes-ia64-arch-specific-handling-of-kprobes-fix.patch
-kprobes-ia64-architecture-specific-support.patch -kprobes-ia64-support-kprobe-on-branch-call-instructions.patch
-kprobes-ia64-cleanup.patch
-kprobes-ia64-qp-fix.patch
-kprobes-ia64-cleanup-2.patch
-kprobes-ia64-cmp-ctype-unc-support.patch # fold
-kprobes-ia64-safe-register-kprobe.patch
-kprobes-ia64-check-jprobe-break-before-handling.patch -kprobes-temporary-disarming-of-reentrant-probe.patch -kprobes-temporary-disarming-of-reentrant-probe-for-i386.patch -kprobes-temporary-disarming-of-reentrant-probe-for-x86_64.patch -kprobes-temporary-disarming-of-reentrant-probe-for-x86_64-fix.patch -kprobes-temporary-disarming-of-reentrant-probe-for-ppc64.patch -kprobes-temporary-disarming-of-reentrant-probe-for-sparc64.patch -kprobes-temporary-disarming-of-reentrant-probe-for-ia64.patch -allow-a-jprobe-to-coexist-with-muliple-kprobes.patch
-setuid-core-dump.patch
-support-for-dx-directories-in-ext3_get_parent-nfsd.patch -document-the-fact-that-linux-arm-kernel-is-subscribers-only.patch -add-some-comments-to-lookup_create.patch
-fix-of-bogus-file-max-limit-messages.patch
-software-suspend-and-recalc-sigpending-bug-fix.patch
-o1-sb-list-traversing-on-syncs.patch
-26-altix-shut-off-xmit-intr-if-done-xmitting.patch
-parport-netmos-nm9855-fix.patch
-dont-force-o_largefile-for-32-bit-processes-on-ia64-2612-rc3.patch
-ide-floppy-adjustments.patch
-adjust-per_cpu-definition-in-non-smp-case.patch
-apply-quotation-handling-to-makefilebuild.patch
-mempool-only-init-waitqueue-in-slow-path.patch
#seccomp-disable-tsc-for-seccomp-enabled-tasks.patch
-factor-out-common-code-in-sys_fsync-sys_fdatasync.patch -improve-cd-dvd-packet-driver-write-performance.patch
-remove-eventpoll-macro-obfuscation.patch
-optimize-sys_times-for-a-single-thread-process.patch -optimize-sys_times-for-a-single-thread-process-update.patch -optimize-sys_times-for-a-single-thread-process-update-2.patch -turn-off-sibling-call-optimization-w-frame-pointers.patch -ipcsem-remove-superflous-decrease-variable-from-sys_semtimedop.patch -e1000-numa-aware-allocation-of-descriptors-v2.patch
-gconfig-only-show-scrollbars-if-needed.patch -potential-null-pointer-dereference-in-amiga-serial-driver.patch
-add-offseth-to-dontdiff.patch
-yenta-ti-turn-off-interrupts-during-card-power-on-more-2.patch
-compat-introduce-compat_time_t.patch
-cs4236-irq-handling-fix.patch
-block-add-unlocked_ioctl-support-for-block-devices.patch -pcdp-handle-tables-that-dont-supply-baud-rate.patch
-remove-f_error-field-from-struct-file.patch
-use-drivers-kconfig-for-sparc32.patch
-acl-endianess-annotations.patch
-remove-linux-xattr_aclh.patch
-bug-in-error-recovery-in-fs-bufferc__block_prepare_write.patch
-dpt_i2o-waitqueue-fix.patch
-aio-fix-do_sync_readwrite-to-properly-handle-aio-retries.patch
-aio-make-wait_queue-task-private.patch
-add-note-about-verify_area-removal-to.patch
-ide-cd-reports-current-speed.patch
-pwc-uncompress-warning-fix.patch
-introduce-tty_unregister_ldisc.patch
-convert-users-to-tty_unregister_ldisc.patch
-ibmasm-driver-fix-command-buffer-size.patch
-ibmasm-driver-correctly-wake-up-sleeping-threads.patch -ibmasm-driver-redesign-handling-of-remote-control.patch -ibmasm-driver-redesign-handling-of-remote-control-fix.patch -ibmasm-driver-fix-race-in-command-refcount-logic.patch -autofs4-avoid-panic-on-bind-mount-of-autofs-owned-directory.patch
-autofs4-post-expire-race-fix.patch
-autofs4-bad-lookup-fix.patch
-autofs4-subversion-bump-to-identify-these-changes.patch
-pass-iocb-to-dio_iodone_t.patch
-reiserfs-add-checking-of-journal_begin-return-value.patch
-quota-improve-credits-estimates.patch
-quota-ext3-improve-quota-credit-estimates.patch
-quota-reiserfs-improve-quota-credit-estimates.patch -xtensa-tensilica-xtensa-cpu-arch-maintainer-record.patch -xtensa-architecture-support-for-tensilica-xtensa-part-1.patch -xtensa-architecture-support-for-tensilica-xtensa-part-2.patch -xtensa-architecture-support-for-tensilica-xtensa-part-3.patch -xtensa-architecture-support-for-tensilica-xtensa-part-4.patch -xtensa-architecture-support-for-tensilica-xtensa-part-5.patch -xtensa-architecture-support-for-tensilica-xtensa-part-6.patch -xtensa-architecture-support-for-tensilica-xtensa-part-7.patch -xtensa-architecture-support-for-tensilica-xtensa-part-8.patch -make-reiserfs-bug-on-too-big-transaction.patch
-ipmi-doc-updates-for-ipmi.patch
-ipmi-ipmi-timer-shutdown-cleanup.patch
-ipmi-add-ipmi-power-cycle-capability.patch -ipmi-use-completions-not-semaphores-in-the-ipmi-powerdown-code.patch -ipmi-add-32-bit-ioctl-translations-for-64-bit-platforms.patch
-char-tpm-use-msleep-clean-up-timers.patch
-fix-concerns-with-tpm-driver-use-enums.patch
-fix-tpm-driver-address-missing-const-defs.patch
-fix-tpm-driver-remove-unnecessary-module-stuff.patch
-fix-tpm-driver-read-return-code-issue.patch
-fix-tpm-driver-large-stack-objects.patch
-fix-tpm-driver-how-timer-is-initialized.patch
-fix-tpm-driver-use-to_pci_dev.patch
-fix-tpm-driver-remove-unnecessary-__force.patch
-fix-tpm-driver-sysfs-owernship-changes.patch
-fix-tpm-driver-sysfs-owernship-changes-fix.patch
-fix-tpm-driver-sysfs-owernship-changes-fix-2.patch
-fix-tpm-driver-sysfs-owernship-changes-fix-3.patch
-fix-tpm-driver-add-cancel-function.patch
-fix-tpm-driver-locks.patch
-tpm-support-for-tpms-on-additional-lpc-bus.patch
-tpm-support-for-tpms-on-additional-lpc-bus-fix-2.patch
-tpm-replace-odd-LPC-init-function.patch
-tpm-add-debugging-output.patch
-tpm-improve-output-in-sysfs-files-when-the-tpm-fails.patch -i2o-bugfixes-and-compability-enhancements.patch
-i2o-first-code-cleanup-of-spare-warnings-and-unused.patch -i2o-new-sysfs-attributes-and-adaptec-specific-block.patch -i2o-new-sysfs-attributes-and-adaptec-specific-block-fix.patch -i2o-new-sysfs-attributes-and-adaptec-specific-block-fix-fix.patch -i2o-adaptec-specific-sg_io-access-firmware-access-through.patch -i2o-second-code-cleanup-of-sparse-warnings-and-unneeded.patch -i2o-lindent-run-and-replacement-of-printk-through-osm.patch -i2o-limit-max-sector-workaround-for-promise-controllers.patch
-i2o-build-fix.patch
-i2o-device-attribute-fixes.patch
-drop-obsolete-dibusb-driver.patch
-add-generalized-dvb-usb-driver.patch
-add-generalized-dvb-usb-driver-fix-2.patch
-add-generalized-dvb-usb-driver-fix-3.patch
-add-generalized-dvb-usb-driver-fix-4.patch
-dvb-usb-fix-init-error-checking.patch
-dvb_frontend-use-time_after.patch
-flexcop-add-bcm3510-atsc-frontend-support-for-air2pc-card.patch -flexcop-add-bcm3510-atsc-frontend-support-for-air2pc-card-fix.patch -tuner-corec-improvments-and-ymec-tvision-tvf8533mf.patch
-dvb-documentation-fixes.patch
-oprofile-report-anonymous-region-samples.patch
-nfsd4-find_delegation_file.patch
-nfsd4-nfs4_check_delegmode.patch
-nfsd4-dont-reopen-for-delegated-client.patch
-nfsd4-add-open-state-code-for-claim_delegate_cur.patch
-nfsd4-support-claim_delegate_cur.patch
-nfsd4-fix-fh_expire_type.patch
-nfsd4-block-metadata-ops-during-grace-period.patch
-nfsd4-slabify-nfs4_files.patch
-nfsd4-slabify-stateids.patch
-nfsd4-slabify-delegations.patch
-nfsd4-remove-debugging-counters.patch
-nfsd4-rename-nfs4_file-fields.patch
-nfsd4-reference-count-struct-nfs4_file.patch
-lockd-flush-signals-on-shutdown.patch
-nfs4-hold-filp-while-reading-or-writing.patch
-nfsd4-fix-probe_callback.patch
-nfsd4-nfs4_check_open_reclaim-cleanup.patch
-nfsd4-create-separate-laundromat-workqueue.patch
-nfsd4-simplify-lease-changing.patch
-nfsd4-delegation-recovery.patch
-nfsd4-rename-nfs4_state_init.patch
-nfsd4-clean-up-state-initialization.patch
-nfsd4-remove-nfs4_reclaim_init.patch
-nfsd4-idmap-initialization.patch
-nfsd4-setclientid-simplification.patch
-nfsd4-reboot-hash.patch
-nfsd4-add-find_unconf_by_str-functions-to-simplify-setclientid.patch
-nfsd4-grace-period-end.patch
-nfsd4-make-needlessly-global-code-static.patch
-nfsd4-fix-uncomfirmed-list.patch
-nfsd4-fix-setclientid_confirm-cases.patch
-nfsd4-fix-setclientid_confirm-error-return.patch
-nfsd4-setclientid_confirm-gotoectomy.patch
-nfsd4-setclientid_confirm-comments.patch
-nfsd4-miscellaneous-setclientid_confirm-cleanup.patch
-nfsd4-rename-state-list-fields.patch
-nfsd4-allow-multiple-lockowners.patch
-nfsd4-remove-cb_parsed.patch
-nfsd4-initialize-recovery-directory.patch
-nfsd4-reboot-recovery.patch
-nfsd4-reboot-dirname.patch
-nfsacl-solaris-nfsacl-workaround.patch
-nfs-client-latencies.patch
-rock-lindent.patch
-rock-manual-tidies.patch
-rock-remove-CHECK_SP.patch
-rock-remove-CONTINUE_DECLS.patch
-rock-remove-CHECK_CE.patch
-rock-remove-SETUP_ROCK_RIDGE.patch
-rock-remove-MAYBE_CONTINUE.patch
-rock-remove-MAYBE_CONTINUE-fix.patch
-rock-comment-tidies.patch
-rock-lindent-rock-h.patch
-isofs-remove-debug-stuff.patch
-rock-handle-corrupted-directories.patch
-rock-rename-union-members.patch
-rock-handle-directory-overflows.patch
-rock-handle-directory-overflows-fix.patch -isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags.patch -isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags-tidy.patch -isofs-show-hidden-files-add-granularity-for-assoc-hidden-files-flags-fix.patch -sched2-cleanup-wake_idle.patch
-sched2-improve-load-balancing-pinned-tasks.patch
-sched2-reduce-active-load-balancing.patch
-sched2-fix-smt-scheduling-problems.patch
-sched2-fix-smt-scheduling-problems-fix.patch
-sched2-add-debugging.patch
-sched2-less-aggressive-idle-balancing.patch
-sched2-balance-timers.patch
-sched2-tweak-affine-wakeups.patch
-sched2-no-aggressive-idle-balancing.patch
-sched2-balance-on-fork.patch
-sched2-schedstats-update-for-balance-on-fork.patch
-sched2-sched-tuning.patch
-sched2-sched-tuning-fix.patch
-sched2-sched-domain-sysctl.patch
-sched-uninline-task_timeslice.patch
-sched-cleanup-context-switch-locking.patch
-sched-null-domains.patch
-sched-remove-degenerate-domains.patch
-sched-remove-degenerate-domains-fix.patch
-sched-multilevel-sbe-sbf.patch
-sched-rcu-domains.patch
-sched-rcu-domains-fix.patch
-sched-consolidate-sbe-sbf.patch
-sched-consolidate-sbe-sbf-fix-2.patch
-sched-consolidate-sbe-sbf-fix-3.patch
-sched-relax-pinned-balancing.patch
-sched-micro-optimize-task-requeueing-in-schedule.patch -sched-changing-rt-priority-without-cap_sys_nice.patch
-dynamic-sched-domains-sched-changes.patch
-dynamic-sched-domains-sched-changes-fix.patch
-dynamic-sched-domains-cpuset-changes.patch
-dynamic-sched-domains-ia64-changes.patch
-v4l-saa7134-byteorder-fix.patch
-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
-bttv-support-for-adlink-rtv24-capture-card.patch
-bttv-support-for-adlink-rtv24-capture-card-tidy.patch -bttv-support-for-adlink-rtv24-capture-card-more-tidy.patch
-v4l-saa7134-ntsc-vbi-fix.patch
-v4l-pal-m-chroma-subcarrier-frequency-fix.patch
-video-for-linux-docummentation.patch
-v4l-add-support-for-pixelview-ultra-pro.patch
-dvico-fusionhdtv3-gold-t-documentation-fix.patch
-v4l-support-tuner-thomson-ddt-7611-atsc-ntsc.patch
-bttv-update.patch
-v4l-cx88-cards-update.patch
-v4l-update-for-tuner-cards-and-some-chips.patch
-v4l-update-for-tuner-cards-and-some-chips-fix.patch
-v4l-update-for-saa7134-cards.patch
-v4l-update-for-saa7134-cards-fix.patch
-v4l-update-for-saa7134-cards-fix-2.patch
-gregkh-i2c-i2c-address_range_removal-v4l-fix.patch
-gregkh-i2c-i2c-address_range_removal-v4l-fix-fix.patch
-nfs-patch-for-fscache.patch
-nfs-patch-for-fscache-fixes.patch
-nfs-patch-for-fscache-warning-fix.patch
-x86-rename-apic_mode_exint.patch
-x86-local-apic-fix.patch
-x86_64-e820-64bit.patch
-x86-i8259-shutdown.patch
-x86_64-i8259-shutdown.patch
-x86-apic-virtwire-on-shutdown.patch
-x86_64-apic-virtwire-on-shutdown.patch
-vmlinux-fix-physical-addrs.patch
-x86-vmlinux-fix-physical-addrs.patch
-x86_64-vmlinux-fix-physical-addrs.patch -kexec-x86_64-optimise-storage-of-read-mostly-variables-x86_64-fix.patch
-x86-config-kernel-start.patch
-kexec-reserve-bootmem-fix-for-booting-nondefault-location-kernel.patch
-x86_64-config-kernel-start.patch
-kexec-kexec-generic.patch
-kexec-kexec-generic-maintainers-fix.patch
-kexec-disable-preempt-in-panic.patch
-kexec-kexec-generic-fix.patch
-kexec-kexec-generic-kexec-use-unsigned-bitfield.patch
-x86-machine_shutdown.patch
-x86-kexec.patch
-x86-crashkernel.patch
-x86-crashkernel-fix.patch
-x86_64-machine_shutdown.patch
-x86_64-kexec.patch
-x86_64-kexec-build-fix.patch
-x86_64-crashkernel.patch
-kexec-ppc-support.patch
-kexec-ppc-fix-noret_type.patch
-ppc64-kexec-native-hash-clear.patch
-ppc64-kexec-support-for-ppc64.patch
-x86-crash_shutdown-nmi-shootdown.patch
-x86-crash_shutdown-snapshot-registers.patch
-x86-crash_shutdown-apic-shutdown.patch
-kexec-s390-support.patch
-s390-kexec-fixes.patch
-kdump-export-crash-notes-section-address-through.patch -kdump-export-crash-notes-section-address-through-x86_64-fix.patch -kdump-nmi-handler-segment-selector-stack.patch
-kexec-kexec-on-panic-fix-with-nmi-watchdog-enabled.patch
-kdump-documentation-for-kdump.patch
-kdump-documentation-for-kdump-update.patch
-kdump-documentation-for-kdump-update-fix.patch
-kdump-documentation-update-to-add-gdb-macros.patch
-kdump-retrieve-saved-max-pfn.patch
-kdump-kconfig-for-kdump.patch
-kdump-routines-for-copying-dump-pages.patch
-kdump-retrieve-elfcorehdr-address-from-command.patch
-kdump-access-dump-file-in-elf-format.patch
-kdump-parse-elf32-headers-and-export-through.patch
-kdump-accessing-dump-file-in-linear-raw-format.patch
-kdump-cleanups-for-dump-file-access-in-linear.patch -kdump-sysrq-trigger-mechanism-for-kexec-based-crashdumps.patch -kdump-use-real-pt_regs-from-exception.patch
-kdump-use-real-pt_regs-from-exception-fix.patch
-kdump-use-real-pt_regs-from-exception-fix-fix.patch
-kdump-save-trap-information-for-later-analysis.patch
-kexec-code-cleanup.patch
-serial-eliminate-magic-numbers.patch
-bring-back-tux-on-chips-65550-framebuffer.patch
-s1d13xxxfb-linkage-fix.patch
-some-vesafb-fixes.patch
-intelfbdrv-naming-fix.patch
-fbdev-iomove-removal.patch
-pm3fb-typo-fix.patch
-vga-to-fbcon-fix.patch
-intelfb-add-voffset-option-to-avoid-conficts-with-xorg-i810-driver.patch -intelfb-add-voffset-option-to-avoid-conficts-with-xorg-i810-driver-fix.patch -intelfb-fix-accel-detection-when-changing-video-modes.patch
-intelfb-documentation.patch
-intelfb-documentation-fix.patch
-framebuffer-driver-for-arc-lcd-board.patch
-framebuffer-driver-for-arc-lcd-board-tidy.patch
-framebuffer-driver-for-arc-lcd-board-update.patch
-new-pci-id-for-chipsfb.patch
-new-framebuffer-fonts-updated-12x22-font-available.patch
-fbdev-stack-reduction.patch
-fbdev-fill-in-the-access_align-field.patch -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 -md-merge-md_enter_safemode-into-md_check_recovery.patch -md-improve-locking-on-safemode-and-move-superblock-writes.patch -md-improve-the-interface-to-sync_request.patch -md-optimised-resync-using-bitmap-based-intent-logging.patch -md-optimised-resync-using-bitmap-based-intent-logging-mempool-fix.patch -md-a-couple-of-tidyups-relating-to-the-bitmap-file.patch
-md-call-bitmap_daemon_work-regularly.patch -md-print-correct-pid-for-newly-created-bitmap-writeback-daemon.patch -md-minor-code-rearrangement-in-bitmap_init_from_disk.patch -md-make-sure-md-bitmap-is-cleared-on-a-clean-start.patch
-md-printk-fix.patch
-md-improve-debug-printing-of-bitmap-superblock.patch -md-check-return-value-of-write_page-rather-than-ignore-it.patch -md-enable-the-bitmap-write-back-daemon-and-wait-for-it.patch -md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared.patch -md-optimised-resync-using-bitmap-based-intent-logging-fix.patch -md-raid1-support-for-bitmap-intent-logging.patch -md-fix-bug-when-raid1-attempts-a-partial-reconstruct.patch -md-raid1-support-for-bitmap-intent-logging-fix.patch -md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch -md-fix-deadlock-due-to-md-thread-processing-delayed-requests.patch -md-allow-md-intent-bitmap-to-be-stored-near-the-superblock.patch -md-allow-md-to-update-multiple-superblocks-in-parallel.patch -md-allow-md-to-update-multiple-superblocks-in-parallel-fix.patch -md-two-small-fixes-for-md-verion-1-superblocks.patch -md-dont-skip-bitmap-pages-due-to-lack-of-bit-that-we-just-cleared-fix.patch -md-remove-unneeded-null-checks-before-kfree.patch
-modules-add-version-and-srcversion-to-sysfs.patch
-modules-add-version-and-srcversion-to-sysfs-fix.patch -modules-add-version-and-srcversion-to-sysfs-fix-2.patch -modules-add-version-and-srcversion-to-sysfs-fix-3.patch
-detect-atomic-counter-underflows.patch
-docbook-build-fix.patch
-docbook-only-use-tabular-style-for-long-synopsis.patch
-docbook-update-comments.patch
-xip-bdev-execute-in-place-3rd-version.patch
-xip-fs-mm-execute-in-place-3rd-version.patch
-xip-fs-mm-execute-in-place-3rd-version-fix.patch
-xip-ext2-execute-in-place-3rd-version.patch
-xip-ext2-execute-in-place-3rd-version-fixes.patch
-xip-reduce-code-duplication.patch
-xip-madvice-fadvice-execute-in-place-3rd-version.patch
-xip-description.patch
-drivers-media-video-tvaudioc-make-some-variables-static.patch -kernel-irq-spuriousc-make-a-function-static.patch
-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
-drivers-media-common-saa7146_fopsc-make-a-function-static.patch
-net-sctp-make-two-functions-static.patch
-drivers-isdn-sc-possible-cleanups.patch
-drivers-isdn-pcbit-possible-cleanups.patch
-drivers-isdn-i4l-possible-cleanups.patch
-unexport-mca_find_device_by_slot.patch
-drivers-isdn-hardware-avm-misc-cleanups.patch
-drivers-isdn-act2000-capic-if-0-an-unused-function.patch
-x86-64-add-memcpy-memset-prototypes.patch
-au1100fb-convert-to-c99-inits.patch
-riottyc-cleanups-and-warning-fix.patch
-char-ds1620-use-msleep-instead-of-schedule_timeout.patch -char-tty_io-replace-schedule_timeout-with-msleep_interruptible.patch -kernel-timer-fix-msleep_interruptible-comment.patch
-init-do_mounts_initrdc-fix-sparse-warning.patch
-arch-i386-kernel-trapsc-fix-sparse-warnings.patch
-arch-i386-kernel-apmc-fix-sparse-warnings.patch
-arch-i386-mm-faultc-fix-sparse-warnings.patch
-arch-i386-crypto-aesc-fix-sparse-warnings.patch
-small-partitions-msdos-cleanups.patch
-remove-redundant-null-check-before-before-kfree-in.patch -get-rid-of-redundant-null-checks-before-kfree-in-arch-i386.patch -remove-redundant-null-checks-before-kfree-in-sound-and.patch
-drivers-scsi-initioc-cleanups.patch
-dont-do-pointless-null-checks-and-casts-before-kfree.patch
-drivers-char-isicomc-section-fixes.patch
-sound-oss-cleanups.patch
-sound-oss-cleanups-fix.patch
-sound-oss-rme96xxc-remove-kernel-22-ifs.patch
-drivers-char-mwave-tp3780ic-remove-kernel-22-ifs.patch -serial-icom-remove-custom-msescs_to_jiffies-macro.patch
-printk-drivers-char-applicomc.patch
-printk-drivers-char-ftape-compressor-zftape-compressc.patch
-lib-sha1c-fix-sparse-warning.patch
-x86_64-coding-style-and-whitespace-fixups.patch
-use-align-to-remove-duplicate-code.patch -cosmetic-fixes-for-example-programs-in-documentation-cdrom-sbpcd.patch -drivers-scsi-dpt-remove-versionh-dependencies.patch
-sound-oss-sscapec-remove-dead-code.patch
-drivers-char-istallionc-remove-an-unneeded-variable.patch
-drivers-char-mwave-3780ic-cleanups.patch
-drivers-char-nvramc-possible-cleanups.patch
-drivers-char-rocketc-cleanups.patch
-fs-jffs-cleanups.patch
-fs-ncpfs-remove-unused-ifdef-use_old_slow_directory_listing-code.patch -drivers-block-sx8c-remove-unused-code.patch
-drivers-video-matrox-matroxfb_miscc-remove-dead-code.patch -drivers-char-mwave-tp3780ic-remove-dead-code.patch
-drivers-block-ll_rw_blkc-cleanups.patch
-change-the-sound_prime-handling.patch
-i386-cleanup-boot_cpu_logical_apicid-variables.patch
-update-computone-maintainers-entry.patch
-remove-pointless-null-check-before-kfree-in-sony535c.patch
-kfree-cleanups-in-ixjc.patch
-kfree-cleanups-for-drivers-firmware.patch
-drivers-char-ip2-cleanups.patch
-drivers-cdrom-cm206c-cleanups.patch
-drivers-isdn-hisax-possible-cleanups.patch
-ll_merge_requests_fn-cleanup.patch
-update-comment-about-gzip-scratch-size.patch
-kill-signed-chars.patch
-printk-arch-i386-mm-pgtablec.patch
-printk-arch-i386-mm-ioremapc.patch
-sound-oss-esssolo1-use-the-dma_32bit_mask-constant.patch -sound-oss-es1371-use-the-dma_32bit_mask-constant.patch -sound-oss-es1370-use-the-dma_32bit_mask-constant.patch -sound-oss-cmpci-use-the-dma_32bit_mask-constant.patch -remove-duplicate-file-in-documentation-networking-drivers_net_wan_kconfig.patch -remove-duplicate-file-in-documentation-networking-00-index.patch -remove-duplicate-file-in-documentation-networking.patch -remove-redundant-info-from-submittingpatches.patch
Merged
-aic79xx-deadlock-fix.patch
-aic79xx-deadlock-fix-2.patch
-aic79xx-deadlock-fix-3.patch
Dropped - it was fixed differently.
+jffs2-build-fix.patch
+arm-swsusp-build-fix.patch
Fix damage from recent swsusp cleanups
-ia64-disable-preempt.patch
Dropped: unneeded
+alsa-maestro3-div-by-zero-fix.patch
Revert an alsa change which appears to cause a divide-by-zero.
-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-ipmi-class_simple-fixes.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-driver-model-documentation-update.patch -gregkh-driver-libfs-add-simple-attribute-files.patch -gregkh-driver-driver-fix-error-handling-in-bus_add_device.patch -gregkh-driver-driver-device_attr-01.patch -gregkh-driver-driver-device_attr-02.patch -gregkh-driver-driver-device_attr-03.patch -gregkh-driver-driver-device_attr-04.patch -gregkh-driver-driver-device_attr-05.patch -gregkh-driver-driver-device_attr-06.patch -gregkh-driver-driver-device_attr-07.patch -gregkh-driver-driver-device_attr-08.patch -gregkh-driver-driver-device_attr-09.patch -gregkh-driver-driver-device_attr-10.patch -gregkh-driver-driver-device_attr-11.patch -gregkh-driver-driver-device_attr-12.patch -gregkh-driver-driver-device_attr-i2c-sysfs.h.patch -gregkh-driver-driver-device_attr-i2c-adm1026.patch -gregkh-driver-sysfs-permissions-01.patch -gregkh-driver-sysfs-permissions-02.patch -gregkh-driver-sysfs-permissions-03.patch -gregkh-driver-dont-loose-devices-on-suspend-failure.patch -gregkh-driver-sysfs-page_size-check.patch +gregkh-driver-driver-bus_find_device.patch +gregkh-driver-driver-unbind.patch +gregkh-driver-driver-bind.patch +gregkh-driver-driver-bus_rescan_devices-nocount.patch
Greg's driver core tree
-gregkh-i2c-i2c-address_range_removal.patch -gregkh-i2c-i2c-address_merge_video.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 -gregkh-i2c-i2c-adm9240-cleanup.patch -gregkh-i2c-i2c-jiffies.h.patch -gregkh-i2c-i2c-macro-abuse-cleanup.patch -gregkh-i2c-i2c-via686a-code-cleanup.patch -gregkh-i2c-i2c-adm1021-remove_die_code.patch -gregkh-i2c-i2c-Kconfig-corrections.patch -gregkh-i2c-i2c-macro-abuse-cleanup-via686a.patch -gregkh-i2c-i2c-driver-device_attr-fixup.patch -gregkh-i2c-i2c-spelling-fixes-more-01.patch -gregkh-i2c-i2c-spelling-fixes-more-02.patch -gregkh-i2c-i2c-spelling-fixes-more-03.patch -gregkh-i2c-i2c-spelling-fixes-more-04.patch -gregkh-i2c-i2c-mpc-race-fix.patch -gregkh-i2c-i2c-mailing-list-move.patch -gregkh-i2c-i2c-tps6501x.patch -gregkh-i2c-i2c-docs-update-1.patch -gregkh-i2c-i2c-docs-update-2.patch -gregkh-i2c-i2c-docs-update-3.patch -gregkh-i2c-i2c-Kconfig-update.patch -gregkh-i2c-i2c-pcf8574-cleanup.patch -gregkh-i2c-i2c-adm9240-docs.patch -gregkh-i2c-i2c-device-attr-lm90.patch -gregkh-i2c-i2c-device-attr-lm83.patch -gregkh-i2c-i2c-device-attr-lm63.patch -gregkh-i2c-i2c-device-attr-it87.patch -gregkh-i2c-i2c-max6875.patch -gregkh-i2c-i2c-rename-i2c-sysfs.patch -gregkh-i2c-i2c-pca9539.patch -gregkh-i2c-i2c-ds1374-01.patch -gregkh-i2c-i2c-ds1374-02.patch -gregkh-i2c-i2c-ds1374-03.patch -gregkh-i2c-i2c-w83781d-remove-non-i2c-chips.patch -gregkh-i2c-w1-ds18xx_sensors.patch -gregkh-i2c-w1-new_rom_family.patch -gregkh-i2c-w1-cleanups.patch -gregkh-i2c-w1-new-family-structure.patch -gregkh-i2c-w1-build-fixups.patch -gregkh-i2c-w1-remove-dup-family-id.patch -gregkh-i2c-w1-01.patch
-gregkh-i2c-w1-02.patch
-gregkh-i2c-w1-03.patch
-gregkh-i2c-w1-04.patch
-gregkh-i2c-w1-05.patch
-gregkh-i2c-w1-06.patch
-gregkh-i2c-w1-07.patch
Greg's i2c tree
+i2c-new-max6875-driver-may-corrupt-eeproms.patch
i2c eeprom corruption fix
+git-libata-adma-mwi.patch
+git-libata-chs-support.patch
+git-libata-passthru.patch
+git-libata-promise-sata-pata.patch
Bring these libata trees back
+samsung-sn-124-works-perfectly-well-with-dma-on-sata-too.patch
SATA fix
+git-netdev-janitor-fixup.patch
Fix rejects in git-netdev-janitor.patch
+ipw2100-remove-by-hand-function-entry-exit-debugging.patch +ipw2100-remove-commented-out-code.patch +pcnet_csc-irq-handler-optimization.patch +is_multicast_ether_addr-hack.patch +wireless-device-attr-fixes.patch +wireless-device-attr-fixes-2.patch +ipw2100-old-gcc-fix.patch
Various netdev fixups
-git-ocfs.patch
+git-ocfs2.patch
Renamed this patch
+gregkh-pci-pci-fix-drivers-setting-shutdown.patch
Addition to Greg's PCI tree
+gregkh-pci-pci-assign-unassigned-resources-fix.patch
Try to fix it
+revert-gregkh-pci-pci-assign-unassigned-resources.patch
Revert a bad patch in it
+pci-yenta-cardbus-fix.patch
Try to fix the `resource 0 busy, reconfiguring...' bug
+git-scsi-block.patch
+git-scsi-block-fix.patch
New git tree (James Bottomley)
+scsi-ahc_target_state-check-starget-valid.patch
adaptec driver fix
-gregkh-usb-usb-driver-device_attr-fixup.patch +gregkh-usb-usb-storage-port-reset-on-transport-error.patch
Changes in Greg's USB tree.
-swapspace-layout-improvements.patch
Dropped again. Reasonable idea, no net benefit observable, not anough time to work on it, gets in the way.
+mm-consolidate-get_order.patch
clean up the get_order() implementations
-proc-pid-smaps-fix.patch
-proc-pid-smaps-tidy.patch
-proc-pid-smaps-fix-fix.patch
Folded into proc-pid-smaps.patch
+ppp-handle-misaligned-accesses.patch +ipvs-add-and-reorder-bh-locks-after-moving-to-keventd.patch +ipvs-close-race-conditions-on-ip_vs_conn_tab-list-modification.patch +ipvs-close-race-conditions-on-ip_vs_conn_tab-list-modification-fix.patch +zatm-kfree-fix.patch
Various net fixes
-cs89x0c-support-for-philips-pnx0105-network-adapter-tidy.patch
Folded into cs89x0c-support-for-philips-pnx0105-network-adapter.patch
+silence-cs89x0.patch
Kill a printk
+x86-i8253-i8259a-lock-cleanup.patch
x86 code cleanup
+seccomp-tsc-disable.patch
Disable tsc on processes which are running under seccomp
-mempool-bounce-buffer-restriction.patch
Not sure that I'll merge this - the problem is real but this implementation is perhaps not the best wrt SMP scalability.
+add-suspend-resume-for-timer.patch
Add suspend and resume support for x86 timers
+cris-update-1-17-arch-split.patch +cris-update-2-17-configuration-and-build.patch +cris-update-3-17-console.patch +cris-update-4-17-debug.patch +cris-update-5-17-drivers.patch +cris-update-6-17-i-o-and-dma-allocator.patch +cris-update-7-17-irq.patch +cris-update-8-17-misc-patches.patch +cris-update-9-17-mm.patch +cris-update-10-17-pci.patch +cris-update-11-17-profiler.patch +cris-update-12-17-serial-port-driver.patch # rmk said no +cris-update-13-17-smp.patch +cris-update-14-17-synchronous-serial-port-driver.patch +cris-update-15-17-updates-for-2612.patch +cris-update-16-17-usb.patch +cris-update-17-17-new-subarchitecture-v32.patch
arch/cris updates
+uml-kill-some-useless-vmalloc-tlb-flushing.patch
+uml-remove-winch-sem.patch # "keep in -mm"
uml updates
-detect-soft-lockups-smp_processor_id-cleanup-fix.patch -detect-soft-lockups-from-touch_nmi_watchdog.patch -kernel-softlockup-fix-usage-of-msleep_interruptible.patch -turn-soft-lock-off-when-panicking.patch
Folded into detect-soft-lockups.patch
-relayfs-properly-handle-oversized-events.patch
-relayfs-backing_dev-fix.patch
Folded into relayfs.patch
+relayfs-cancel-work-on-close-reset.patch +relayfs-add-private-data-to-channel-struct.patch +relayfs-function-docfix.patch +relayfs-add-relayfs-website-to-documentation.patch
relayfs fixes
-fix-of-dcache-race-leading-to-busy-inodes-on-umount-fix.patch -fix-of-dcache-race-leading-to-busy-inodes-on-umount-tidy.patch
Folded into fix-of-dcache-race-leading-to-busy-inodes-on-umount.patch
+using-msleep-instead-of-hz.patch
+using-msleep-instead-of-hz-fix.patch
+using-msleep-instead-of-hz-fix-2.patch
cleanup
+new-driver-for-yealink-usb-p1k-phone.patch +new-driver-for-yealink-usb-p1k-phone-tidy.patch +new-driver-for-yealink-usb-p1k-phone-fixes.patch +new-driver-for-yealink-usb-p1k-phone-warning-sysfs-fixes.patch +yealink-maintainer.patch
USB phone driver
+usb-makefile-update-for-sisusbvga.patch
USB fix
+drivers-char-tiparc-off-by-one-array-access.patch
tipar.c fix
+ixp4xx-ixp2000-watchdog-driver-typo.patch
Fix typos in two watchdog drivers
+de_thread-eliminate-unneccessary-sighand-locking.patch
Locking simplification
+pselect-ppoll-system-calls.patch
+pselect-ppoll-system-calls-tidy.patch
+pselect-ppoll-system-calls-fix.patch
+pselect-ppoll-system-calls-sigset_t-fix-2.patch
pselect() and ppoll() (the case seems thin)
+itimer_real-fix-possible-deadlock-and-race.patch
itimer deadlock fix
+pcie-acpi-tg3-ethernet-not-coming-back-properly-after-s3-suspendon-dellm70.patch
pcie power management fix
+adapt-drivers-char-vt_ioctlc-to-non-x86.patch
Don't use a hardwired number for clock speed
+request_firmware-avoid-race-conditions.patch
request_firmware() fixes
+yenta-make-topic95-bridges-work-with-16bit-cards.patch
cardbus fix
+smsc-ircc2-whitespace-fixes.patch +smsc-ircc2-formatting-fixes.patch +smsc-ircc2-drop-dim-macro-in-favor-of-array_size.patch +smsc-ircc2-remove-typedefs.patch +smsc-ircc2-dont-pass-iobase-around.patch +smsc-ircc2-add-to-sysfs-as-platform-device-new-pm.patch +smsc-ircc2-pm-cleanup-do-not-close-device-when-suspending.patch +smsc-ircc2-pm-cleanup-do-not-close-device-when-suspending-fixes.patch +smsc-ircc2-use-netdev_priv.patch +smsc-ircc2-dont-use-void-where-specific-type-will-do.patch
irda driver updates
+ib-mthca-add-sun-copyright-notice.patch +ib-mthca-clean-up-error-messages.patch +ib-mthca-clean-up-cq-debug.patch +ib-mthca-use-dma_alloc_coherent-instead-of-pci_alloc_consistent.patch +ib-mthca-set-qp-static-rate-correctly.patch +ib-mthca-set-rdma-atomic-capabilities-correctly.patch +ib-mthca-enable-unreliable-connected-transport.patch +ib-mthca-fix-memset-size.patch +ib-mthca-move-mthca_is_memfree-checks.patch +ib-mthca-split-off-mtt-allocation.patch +ib-mthca-fix-memory-leak-on-error-path.patch +ib-mthca-encapsulate-command-interface-init.patch +ib-mthca-align-fw-command-mailboxes-to-4k.patch +ib-mthca-bump-version.patch
+ib-fix-race-in-sa_query.patch +ib-fix-pack-unpack-when-size_bits-==-64.patch +maintainers-update-roland-dreiers-email.patch
Infiniband updates
+cciss-26-pci-id-fix.patch +cciss-26-pci-domain-info-pass-2.patch +cciss-26-remove-partition-info-from-cciss_getluninfo.patch +cciss-26-remove-partition-info-from-cciss_getluninfo-fix.patch
cciss fixes
+headers-enable-ppc64-___arch__swab16-and-___arch__swab32.patch +headers-include-linux-compilerh-for-__user.patch +headers-include-linux-typesh-for-usb_ch9h.patch
Header file cleanups
+coverity-i386-build-negative-return-to-unsigned-fix.patch +coverity-i386-scsi_lib-buffer-overrun-fix.patch +coverity-fs-udf-namei-null-check.patch +coverity-fs-ext3-super-match_int-return-check.patch +coverity-desc-bitmap-overrun-fix.patch +coverity-tty_ldisc_ref-return-null-check.patch
Various fixes found by the Coverity checker.
+kprobes-fix-single-step-out-of-line-take2.patch +return-probe-redesign-architecture-independant-changes.patch +return-probe-redesign-i386-specific-changes.patch +return-probe-redesign-x86_64-specific-changes.patch +return-probe-redesign-ia64-specific-implementation.patch +return-probe-redesign-ppc64-specific-implementation.patch +kprobes-ia64-refuse-inserting-kprobe-on-slot-1.patch +kprobes-ia64-refuse-kprobe-on-ivt-code.patch
kprobes updates
-rapidio-support-core-base-rapidio-support-core-base.patch
Folded into rapidio-support-core-base.patch
-rapidio-support-ppc32-fix.patch -rapidio-support-ppc32-add-error-checking-to-mpc85xx.patch
Folded into rapidio-support-ppc32.patch
-dlm-lockspaces-callbacks-directory-dlm-consistent-ifdefs.patch -dlm-lockspaces-callbacks-directory-build-fix.patch -dlm-lockspaces-callbacks-directory-fix.patch -dlm-lockspaces-callbacks-directory-fix-2.patch -dlm-lockspaces-callbacks-directory-fix-2-dlm-dont-repeat-include.patch -dlm-lockspaces-callbacks-directory-fix-3.patch -dlm-lockspaces-callbacks-directory-dlm-dont-free-lvb-twice.patch
Folded into dlm-lockspaces-callbacks-directory.patch
-dlm-communication-dlm-dont-add-duplicate-node-addresses.patch
Folded into dlm-communication.patch
-dlm-recovery-dlm-timer-cant-be-global.patch
-dlm-recovery-dlm-clear-recovery-flags.patch
Folded into dlm-recovery.patch
-dlm-device-interface-fix.patch -dlm-device-interface-dlm-uncomment-unregister_lockspace.patch -dlm-device-interface-dlm-newline-in-printks.patch
Folded into dlm-device-interface.patch
-dlm-debug-fs-no-debug-build-fix.patch
-dlm-debug-fs-dlm-consistent-ifdefs.patch
Folded into dlm-debug-fs.patch
-connector-warning-fixes.patch
-connector-export-initialization-flag.patch
-connector-netlink-id-fix.patch
-connector-remove-socket-number-parameter.patch
Folded into connector.patch
-connector-add-a-fork-connector-build-fix.patch -fork-connector-send-status-to-userspace.patch -fork-connector-send-status-to-userspace-fix.patch
Folded into connector-add-a-fork-connector.patch
+connector-add-a-fork-connector-use-after-free-fix.patch
Fix connector-add-a-fork-connector.patch
+inotify-faq-fds.patch
Update the inotify FAQ
-ext3-reduce-allocate-with-reservation-lock-latencies-tidy.patch
Folded into ext3-reduce-allocate-with-reservation-lock-latencies.patch
-pcmcia-allow-function-id-based-match-fix.patch
Folded into pcmcia-allow-function-id-based-match.patch
+pcmcia-id_table-for-ide_csc-update.patch +pcmcia-more-ids-for-tdk-multifunction-cards.patch
More pcmcia ID tables
-pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices-fix.patch
Folded into pcmcia-mark-parent-bridge-windows-as-resources-available-for-pcmcia-devices.patch
-pcmcia-move-pcmcia-ioctl-to-a-separate-file-fix.patch
Folded into pcmcia-move-pcmcia-ioctl-to-a-separate-file.patch
-pcmcia-clean-up-cs-ds-callback-fix.patch
Folded into pcmcia-clean-up-cs-ds-callback.patch
+pcmcia-8-and-16-bit-access-for-static_map.patch
+pcmcia-export-modalias-in-sysfs.patch
pcmcia fixes
+nfs-fix-client-oops-when-debugging-is-on.patch
+ingo-nfs-stuff.patch
+xdr-input-validation.patch
nfs fixes
+spinlock-consolidation.patch
+spinlock-consolidation-parisc-build-fixes.patch
+spinlock-consolidation-sparc64-fix.patch
Clean up the spinlock code
-kgdb-move-config-option-for-bad_syscall_exit.patch -kgdb-fix-bad_syscall_exit-lockup.patch -kgdb-x86-config_debug_info-fix.patch
Folded into kgdb-ga.patch
-kgdb-x86_64-support-fix.patch
-kgdb-x86_64-config_debug_info-fix.patch
Folded into kgdb-x86_64-support.patch
-numa-aware-slab-allocator-v3-__bad_size-fix.patch
Folded into numa-aware-slab-allocator-v5.patch
+numa-aware-slab-allocator-unifdeffery.patch
Reduce ifdefs in numa-aware-slab-allocator-v5.patch
+iteraid-fix-trivial-sparse-warnings.patch
+iteraid-misc-trivial-cleanups.patch
+iteraid-remove-home-grown-memmove.patch
+iteraid-memset-fix.patch
Fixes against iteraid.patch
-silence-spinlock-rwlock-uninitialized-break_lock-member.patch
Dropped - lots of rejects and might no longer be needed and I'm not very interested in `gcc -W' fixes.
-nmi-lockup-and-altsysrq-p-dumping-calltraces-on-_all_-cpus-fix.patch
Folded into nmi-lockup-and-altsysrq-p-dumping-calltraces-on-_all_-cpus.patch
-perfctr-ppc64-wraparound-fixes.patch -perfctr-x86-update-with-k8-multicore-fixes-take-2.patch -perfctr-seqlocks-for-mmaped-state-common.patch -perfctr-seqlocks-for-mmaped-state-x86.patch -perfctr-seqlocks-for-mmaped-state-ppc64.patch -perfctr-seqlocks-for-mmaped-state-ppc32.patch
Folded into perfctr.patch
+perfctr-handle-non-of-ppc32-platforms.patch
perfctr update
+sched-tweak-idle-thread-setup-semantics.patch +sched-run-sched_normal-tasks-with-real-time-tasks-on-smt-siblings.patch +max_user_rt_prio-and-max_rt_prio-are-wrong.patch +sched-idlest-cpus_allowed-aware.patch
+sched-cleanups.patch
+sched-task_noninteractive.patch +scheduler-cache-hot-autodetect.patch # needs work +scheduler-cache-hot-autodetect-section-fix.patch +scheduler-cache-hot-autodetect-x86-cpu_khz-type-fix.patch +scheduler-cache-hot-autodetect-x86-cpu_khz-type-fix-2.patch +sched-add-cacheflush-asm.patch +sched-add-cacheflush-asm-2.patch +sched-add-cacheflush-asm-2-ia64-fix.patch +scheduler-cache-hot-autodetect-build-fix.patch +sched-fix-smt-scheduler-latency-bug.patch
scheduler stuff
+v4l-maintainer-patch.patch +v4l-tuner-improvements.patch +v4l-bttv-new-insmod-parameters.patch +v4l-api-new-webcam-formats-included.patch +v4l-documentation-changes-mostly-new-cards-included.patch
v4l updates
-allow-x86_64-to-reenable-interrupts-on-contention.patch
Dropped - it had rejects and Andi didn't like it anyway.
-numa-policies-for-file-mappings-mpol_mf_move-cachefs.patch -cachefs-release-search-records-lest-they-return-to-haunt-us.patch -fix-64-bit-problems-in-cachefs.patch -cachefs-fixed-typos-that-cause-wrong-pointer-to-be-kunmapped.patch -cachefs-return-the-right-error-upon-invalid-mount.patch -fix-cachefs-barrier-handling-and-other-kernel-discrepancies.patch -remove-error-from-linux-cachefsh.patch -cachefs-warning-fix-2.patch -cachefs-linkage-fix-2.patch
-cachefs-build-fix.patch
Folded into cachefs-filesystem.patch
-add-page-becoming-writable-notification-fix.patch -add-page-becoming-writable-notification-build-fix.patch -make-page-becoming-writable-notification-a-vma-op-only.patch
Folded into add-page-becoming-writable-notification.patch
-provide-a-filesystem-specific-syncable-page-bit-fix.patch -provide-a-filesystem-specific-syncable-page-bit-fix-2.patch
Folded into provide-a-filesystem-specific-syncable-page-bit.patch
-afs-cachefs-dependency-fix.patch
Folded into make-afs-use-cachefs.patch
-split-general-cache-manager-from-cachefs-fix.patch
Folded into split-general-cache-manager-from-cachefs.patch
-make-page-becoming-writable-notification-a-vma-op-only-kafs-fix-fix.patch
Folded into make-page-becoming-writable-notification-a-vma-op-only-kafs-fix.patch
+files-break-up-files-struct-fix-dupfd-by-fdt-reload.patch +files-files-struct-with-rcu-change-fd_install-assertion.patch +files-files-locking-doc-update.patch
Fixes for the files_lock RCUification patches in -mm.
+asfs-filesystem-driver.patch
+asfs-filesystem-driver-fixes.patch
Amiga smart filesystem driver. Needs cleanups and I don't think we see a lot of demand for this one.
+reiser4-swsusp-build-fix.patch
+reiser4-printk-warning-fix.patch
+reiser4-fix-dependencies.patch
reiser4 fixes
+v9fs-vfs-file-dentry-and-directory-operations-fix-fsf-postal-address-in-source-headers.patch +v9fs-vfs-inode-operations-fix-fsf-postal-address-in-source-headers.patch +v9fs-vfs-superblock-operations-and-glue-fix-fsf-postal-address-in-source-headers.patch +v9fs-9p-protocol-implementation-fix-fsf-postal-address-in-source-headers.patch +v9fs-transport-modules-fix-fsf-postal-address-in-source-headers.patch +v9fs-transport-modules-fix-timeout-segfault-corner-case.patch +v9fs-debug-and-support-routines-fix-fsf-postal-address-in-source-headers.patch +v9fs-change-error-magic-numbers-to-defined-constants.patch +v9fs-clean-up-vfs_inode-and-setattr-functions.patch +v9fs-fix-support-for-special-files-devices-named-pipes-etc.patch
v9fs updates
+clean-up-the-old-digi-support-and-rescue-it.patch
Clean up the digi driver, make it work on SMP
-minimal-ide-disk-updates.patch +ide-fix-ide-disk-inability-to-handle-lba-only-devices.patch +ide-samsung-sn-124-works-perfectly-well-with-dma.patch +ide-timing-violation-on-reset.patch +ide-generic-allow-for-capture-of-other-unsupported-devices.patch +ide-fix-the-hpt366-driver-layer.patch +ide-fix-crashes-with-hotplug-serverworks.patch +ide-it8212-backport-for-bartlomiej-ide.patch +ide-sensible-probing-for-pci-systems.patch
Various IDE fixes from Alan. This includes Alan's driver for the ITE RAID cards. Presumably you don't want to enable this at the same time as iteraid.patch.
+doc-submitting-corrections-additions.patch
Documentation fixes
-fuse-device-functions-abi-version-change.patch -fuse-device-functions-comments-and-documentation.patch -fuse-device-functions-comments-and-documentation-document-security-measures.patch -fuse-device-functions-cleanup.patch -fuse-device-functions-fuse-serious-information-leak-fix.patch
Folded into fuse-device-functions.patch
-fuse-read-only-operations-multiple-links-to-directory-fix.patch -fuse-read-only-operations-add-offset-to-fuse_dirent.patch -fuse-read-only-operations-readdir-fixes.patch
Folded into fuse-read-only-operations.patch
-fuse-read-write-operations-fix-lookup-forget-interface.patch
Folded into fuse-read-write-operations.patch
-fuse-file-operations-interrupted-open-fix.patch
Folded into fuse-file-operations.patch
-fuse-mount-options-fix.patch -fuse-mount-options-reference-counting-fix.patch -fuse-mount-options-comments-and-documentation.patch -fuse-mount-options-fix-cleanup.patch -fuse-mount-options-fix-fix.patch -fuse-mount-options-remove-allow_root-mount-option.patch
Folded into fuse-mount-options.patch
-fuse-direct-i-o-disable-sendfile-with-direct_io.patch -fuse-direct-i-o-nfsd-with-direct_io-fix.patch -fuse-direct-i-o-fix-warning-on-x86_64.patch
Folded into fuse-direct-i-o.patch
-fuse-add-fsync-operation-for-directories-fix.patch
Folded into fuse-add-fsync-operation-for-directories.patch
+timer-initialization-cleanup-define_timer.patch
Add DEFINE_TIMER, use it.
+more-spin_lock_unlocked-define_spinlock-conversions.patch
A few spinlock initialisation cleanups
number of patches in -mm: 619
number of changesets in external trees: 9
number of patches in -mm only: 618
total patches: 627
All 627 patches:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/patch-list
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
I'm not sure what PCI breakage you're referring to, but a lot of the Cardbus-centric "breakage" isn't a regression - it's new machines with weird PCI BIOS setups being incompatible Linux's current PCI bus handing strategy.
I've been trying to get this fixed for a considerable time, but linux-pci folk seem to be disinterested.
The assumption that the PCI BIOS will sanely assign the PCI bus numbers and that Linux does not need to reassign them is looking increasingly incorrect - most of the Cardbus "why can't the system see my card" are resolved by passing "pci=assign-busses", which causes the PCI subsystem to renumber all PCI busses.
So far, no one who has tried this solution has reported any additional problems that I'm aware of.
Therefore, maybe that should become the default behaviour?
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 9 lines · Russell King
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
I'm not sure what PCI breakage you're referring to, but a lot of the Cardbus-centric "breakage" isn't a regression - it's new machines with weird PCI BIOS setups being incompatible Linux's current PCI bus handing strategy.
Quoted 8 lines
I've been trying to get this fixed for a considerable time, but linux-pci folk seem to be disinterested.
The assumption that the PCI BIOS will sanely assign the PCI bus numbers and that Linux does not need to reassign them is looking increasingly incorrect - most of the Cardbus "why can't the system see my card" are resolved by passing "pci=assign-busses", which causes the PCI subsystem to renumber all PCI busses.
Not the case for where I'm having problems, Toshiba laptop, more info on http://scatter.mine.nu/test/linux-2.6/tosh/
ioports-2.6.12-mm2a 2005-06-27 09:03:44.000000000 +1000 renamed from ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000 +4 -13
@@ -10,20 +10,13 @@ 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 -02f8-02ff : 0000:00:07.0 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial 0cf8-0cff : PCI conf1 -1c00-1cff : 0000:00:07.0 -4000-40ff : PCI CardBus #02 - 4000-407f : 0000:02:00.0 - 4000-407f : xircom_cb -4400-44ff : PCI CardBus #02 -fc00-fcff : 0000:00:0c.0 - fc00-fcff : ESS Maestro +fc00-fcff : ESS Maestro fd00-fd3f : motherboard fe00-fe3f : 0000:00:05.3 fe00-fe3f : motherboard
@@ -40,8 +33,6 @@ fe90-fe97 : motherboard fe9e-fe9e : motherboard feac-feac : motherboard -ff80-ff9f : 0000:00:05.2 - ff80-ff9f : uhci_hcd -fff0-ffff : 0000:00:05.1 - fff0-fff7 : ide0 - fff8-ffff : ide1 +ff80-ff9f : uhci_hcd +fff0-fff7 : ide0 +fff8-ffff : ide1
lilo.conf:
image = /boot/bzImage-2.6.12-mm2a
optional
label = 2.6.12-mm2ap
append="pci=assign-busses"
ioports-2.6.12-mm2ap 2005-06-27 09:06:31.000000000 +1000 renamed from ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000 +4 -13
@@ -10,20 +10,13 @@ 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 -02f8-02ff : 0000:00:07.0 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial 0cf8-0cff : PCI conf1 -1c00-1cff : 0000:00:07.0 -4000-40ff : PCI CardBus #02 - 4000-407f : 0000:02:00.0 - 4000-407f : xircom_cb -4400-44ff : PCI CardBus #02 -fc00-fcff : 0000:00:0c.0 - fc00-fcff : ESS Maestro +fc00-fcff : ESS Maestro fd00-fd3f : motherboard fe00-fe3f : 0000:00:05.3 fe00-fe3f : motherboard
@@ -40,8 +33,6 @@ fe90-fe97 : motherboard fe9e-fe9e : motherboard feac-feac : motherboard -ff80-ff9f : 0000:00:05.2 - ff80-ff9f : uhci_hcd -fff0-ffff : 0000:00:05.1 - fff0-fff7 : ide0 - fff8-ffff : ide1 +ff80-ff9f : uhci_hcd +fff0-fff7 : ide0 +fff8-ffff : ide1
--Grant.
Quoted 2 lines · Grant Coady
Not the case for where I'm having problems, Toshiba laptop, more info on http://scatter.mine.nu/test/linux-2.6/tosh/
Yes in this case. The PCI resources are the ones which say either PCI CardBus, PCI Bus, or are of the format: xxxx:xx:xx.x, and all of them are missing.
The ESS Maestro and others which were below these are driver resources created by the drivers themselves, not the PCI subsystem. Hence these still show up.
Quoted 82 lines
ioports-2.6.12-mm2a 2005-06-27 09:03:44.000000000 +1000 renamed from ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000 +4
-13@@ -10,20 +10,13 @@ 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 -02f8-02ff : 0000:00:07.0 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial 0cf8-0cff : PCI conf1 -1c00-1cff : 0000:00:07.0 -4000-40ff : PCI CardBus #02 - 4000-407f : 0000:02:00.0 - 4000-407f : xircom_cb -4400-44ff : PCI CardBus #02 -fc00-fcff : 0000:00:0c.0 - fc00-fcff : ESS Maestro +fc00-fcff : ESS Maestro fd00-fd3f : motherboard fe00-fe3f : 0000:00:05.3 fe00-fe3f : motherboard@@ -40,8 +33,6 @@ fe90-fe97 : motherboard fe9e-fe9e : motherboard feac-feac : motherboard -ff80-ff9f : 0000:00:05.2 - ff80-ff9f : uhci_hcd -fff0-ffff : 0000:00:05.1 - fff0-fff7 : ide0 - fff8-ffff : ide1 +ff80-ff9f : uhci_hcd +fff0-fff7 : ide0 +fff8-ffff : ide1lilo.conf:
image =/boot/bzImage-2.6.12-mm2a
optional
label = 2.6.12-mm2ap
append="pci=assign-busses"ioports-2.6.12-mm2ap 2005-06-27 09:06:31.000000000 +1000 renamed from ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000 +4
-14@@ -10,20 +10,13 @@ 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 -02f8-02ff : 0000:00:07.0 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial 0cf8-0cff : PCI conf1 -1c00-1cff : 0000:00:07.0 -4000-40ff : PCI CardBus #02 - 4000-407f : 0000:02:00.0 - 4000-407f : xircom_cb -4400-44ff : PCI CardBus #02 -fc00-fcff : 0000:00:0c.0 - fc00-fcff : ESS Maestro +fc00-fcff : ESS Maestro fd00-fd3f : motherboard fe00-fe3f : 0000:00:05.3 fe00-fe3f : motherboard@@ -40,8 +33,6 @@ fe90-fe97 : motherboard fe9e-fe9e : motherboard feac-feac : motherboard -ff80-ff9f : 0000:00:05.2 - ff80-ff9f : uhci_hcd -fff0-ffff : 0000:00:05.1 - fff0-fff7 : ide0 - fff8-ffff : ide1 +ff80-ff9f : uhci_hcd +fff0-fff7 : ide0 +fff8-ffff : ide1 --Grant.
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
I'd like to lobby for the merging into mainline of this patch from git-input. It fixes a real bug, seen by real users, and has been languishing in the input tree since March. It may also be a candidate for the stable tree given it's one-linedness.
--
Fix extraction of HID items >= 32 bits
HID items of width 32 (bits) or greater are incorrectly extracted due to a masking bug in hid-core.c:extract(). This patch fixes it up by forcing the mask to be 64 bits wide.
drivers/usb/input/hid-core.c +1 -1
@@ -757,7 +757,7 @@static __inline____u32 extract (__u8 *report,unsigned offset,unsigned n) { report += (offset >>5 ) <<2 ; offset &=31 ; -return (le64_to_cpu (get_unaligned ((__le64 *)report)) >> offset) & ((1 << n) -1 ); +return (le64_to_cpu (get_unaligned ((__le64 *)report)) >> offset) & ((1ULL << n) -1 ); }static __inline__void implement (__u8 *report,unsigned offset,unsigned n,__u32 value)
Quoted 6 lines · Adam Kropelin
I'd like to lobby for the merging into mainline of this patch from git-input. It fixes a real bug, seen by real users, and has been languishing in the input tree since March. It may also be a candidate for the stable tree given it's one-linedness.
I think we can merge all of git-input into Linus's tree immediately.
But if that'll take some time then sure, we can merge up this little bit.
Quoted 22 lines
Fix extraction of HID items >= 32 bits
HID items of width 32 (bits) or greater are incorrectly extracted due to a masking bug in hid-core.c:extract(). This patch fixes it up by forcing the mask to be 64 bits wide.
Signed-off-by Adam Kropelin <[email protected]>drivers/usb/input/hid-core.c +1
-1@@ -757,7 +757,7 @@static __inline____u32 extract (__u8 *report,unsigned offset,unsigned n) { report += (offset >>5 ) <<2 ; offset &=31 ; -return (le64_to_cpu (get_unaligned ((__le64 *)report)) >> offset) & ((1 << n) -1 ); +return (le64_to_cpu (get_unaligned ((__le64 *)report)) >> offset) & ((1ULL << n) -1 ); }static __inline__void implement (__u8 *report,unsigned offset,unsigned n,__u32 value)
Quoted 11 lines · Andrew Morton
Quoted 6 lines · Adam Kropelin
I'd like to lobby for the merging into mainline of this patch from git-input. It fixes a real bug, seen by real users, and has been languishing in the input tree since March. It may also be a candidate for the stable tree given it's one-linedness.
I think we can merge all of git-input into Linus's tree immediately.
But if that'll take some time then sure, we can merge up this little bit.
I have some minor issues with a few of the patches. I'll take care of that tomorrow, and then it can be merged to Linus.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 6 lines · Andrew Morton
Quoted 4 lines
I'd like to lobby for the merging into mainline of this patch from git-input. It fixes a real bug, seen by real users, and has been languishing in the input tree since March. It may also be a candidate for the stable tree given it's one-linedness.
I think we can merge all of git-input into Linus's tree immediately.
I've checked it, the patches I had originally problems with are already fixed, it's ready for merging.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Hi Andrew,
Can you merge OOPS Reporting Tool
(http://stud.wsi.edu.pl/~piotrowskim/files/ort/beta/ort-b3.tar.bz2)
with next -mm release?
Regards,
Michał Piotrowski
Dominik Brodowski
maintainerACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
In reply to Andrew MortonQuoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
- many resources of devices don't show up in the resource trees ( /proc/iomem and /proc/ioports) any longer. This means that PCMCIA, but also possibly other subsystems (ISA, PnP, ...) do not know which resources it cannot use.
- verify_root_windows() should fail if there are no iomem _or_ ioport resources, not only if there are no iomem _and_ ioport resources.
Nonetheless, with the init-time trouble (hopefully) solved, I'd say that it is time for the PCMCIA patches to get into mainline.
Dominik
Don't auto-configure yenta sockets for PCMCIA devices if it is connected to the root PCI bus on the x86 or x86_64 architectures. Previously, this was handled by the "ioport_resource"/"iomem_resource" check a few lines below, but with the new ACPI-based resource handling this doesn't catch all cases any longer.
drivers/pcmcia/rsrc_nonstatic.c renamed from drivers/pcmcia/rsrc_nonstatic.c.orig +11 -0
@@ -779,6 +779,17 @@if (!s->cb_dev || !s->cb_dev->bus)return -ENODEV ; +#if defined(CONFIG_X86 ) || defined(CONFIG_X86_64 ) +/* If this is the root bus, the risk of hitting +* some strange system devices which aren't protected +* by either ACPI resource tables or properly requested +* resources is too big. Therefore, don't do auto-adding +* of resources at the moment. +*/ +if (s->cb_dev->bus->number ==0 ) +return -EINVAL ; +#endif +for (i=0 ; i <PCI_BUS_NUM_RESOURCES ; i++) { res = s->cb_dev->bus->resource[i];if (!res)
Re: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 5 lines · Dominik Brodowski
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
Quoted 8 lines
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
- many resources of devices don't show up in the resource trees (
/proc/iomemand/proc/ioports) any longer. This means that PCMCIA, but also possibly other subsystems (ISA, PnP, ...) do not know which resources it cannot use.
Is this a recent regression? Is it only in -mm?
IOW: can you identify the bad patch? Or the bad patcher ;)
Quoted 2 lines
-
verify_root_windows()should fail if there are no iomem _or_ ioport resources, not only if there are no iomem _and_ ioport resources.
This too.
Re: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 10 lines · Andrew Morton
Quoted 9 lines · Dominik Brodowski
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
Quoted 8 lines
Quoted 4 lines
- many resources of devices don't show up in the resource trees (
/proc/iomemand/proc/ioports) any longer. This means that PCMCIA, but also possibly other subsystems (ISA, PnP, ...) do not know which resources it cannot use.Is this a recent regression? Is it only in -mm?
IOW: can you identify the bad patch? Or the bad patcher ;)
It's greg's pci-somethingortheotheraboutacpi-collection-02 patch (sorry don't remember it exactly).
It's basically replacing the PCI bus root resources with new resources. These aren't then attached to the resource tree. However, PCI will attach the child resources to the (unattached) bus resources.
Hence, all PCI resources remain invisible.
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Dominik Brodowski
maintainerRe: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
In reply to Andrew MortonQuoted 10 lines · Andrew Morton
Quoted 9 lines · Dominik Brodowski
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
Quoted 6 lines
Quoted 4 lines
- many resources of devices don't show up in the resource trees (
/proc/iomemand/proc/ioports) any longer. This means that PCMCIA, but also possibly other subsystems (ISA, PnP, ...) do not know which resources it cannot use.Is this a recent regression? Is it only in -mm?
Yes. Yes.
Quoted 1 line
IOW: can you identify the bad patch? Or the bad patcher ;)
gregkh-pci-pci-collect-host-bridge-resources-02.patch
Quoted 4 lines
Quoted 2 lines
-
verify_root_windows()should fail if there are no iomem _or_ ioport resources, not only if there are no iomem _and_ ioport resources.This too.
Same one.
Thanks,
Dominik
Re: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 8 lines · Dominik Brodowski
Quoted 1 line
Is this a recent regression? Is it only in -mm?
Yes. Yes.
Quoted 1 line
IOW: can you identify the bad patch? Or the bad patcher ;)
gregkh-pci-pci-collect-host-bridge-resources-02.patch
Guilty as charged. I will look at providing a fix. In the meantime, you can drop this patch if you like Andrew.
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
-
verify_root_windows()should fail if there are no iomem _or_ ioport resources, not only if there are no iomem _and_ ioport resources.
No, I actually saw production (or close to production) machines where BIOS was deliberately only programming memory resources, no IO. In fact, I had to change the check to the current form for such machines.
Rajesh
Dominik Brodowski
maintainerRe: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 8 lines · Rajesh Shah
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
-
verify_root_windows()should fail if there are no iomem _or_ ioport resources, not only if there are no iomem _and_ ioport resources.No, I actually saw production (or close to production) machines where BIOS was deliberately only programming memory resources, no IO. In fact, I had to change the check to the current form for such machines.
Well, what should be done in this case? IMO we should fall back to the "previous" behaviour -- is a
kfree(bus->resource[i]);
bus->resource[i] = bres[i];needed for this to happen?
Thanks,
Dominik
Re: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
In reply to Dominik BrodowskiQuoted 8 lines · Dominik Brodowski
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
Well this patch doesn't do it for Toshiba laptop, ToPIC-100 ZV bridge in 'auto' mode.
"-mm2b" info set on http://scatter.mine.nu/test/linux-2.6/tosh/
ioports-2.6.12-mm2b 2005-06-27 09:54:45.000000000 +1000 renamed from ioports-2.6.12.1a 2005-06-27 09:00:21.000000000 +1000 +4 -13
@@ -10,20 +10,13 @@ 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 -02f8-02ff : 0000:00:07.0 0376-0376 : ide1 0378-037a : parport0 03c0-03df : vesafb 03f6-03f6 : ide0 03f8-03ff : serial 0cf8-0cff : PCI conf1 -1c00-1cff : 0000:00:07.0 -4000-40ff : PCI CardBus #02 - 4000-407f : 0000:02:00.0 - 4000-407f : xircom_cb -4400-44ff : PCI CardBus #02 -fc00-fcff : 0000:00:0c.0 - fc00-fcff : ESS Maestro +fc00-fcff : ESS Maestro fd00-fd3f : motherboard fe00-fe3f : 0000:00:05.3 fe00-fe3f : motherboard
@@ -40,8 +33,6 @@ fe90-fe97 : motherboard fe9e-fe9e : motherboard feac-feac : motherboard -ff80-ff9f : 0000:00:05.2 - ff80-ff9f : uhci_hcd -fff0-ffff : 0000:00:05.1 - fff0-fff7 : ide0 - fff8-ffff : ide1 +ff80-ff9f : uhci_hcd +fff0-fff7 : ide0 +fff8-ffff : ide1
--Grant.
Dominik Brodowski
maintainerRe: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 6 lines · Grant Coady
Quoted 4 lines · Dominik Brodowski
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
Quoted 7 lines
Quoted 4 lines
pci-yenta-cardbus-fix.patch and the following patch should solve the initialization time trouble. However, the ACPI-based PCI resource handling is badly broken, IMHO:
Well this patch doesn't do it for Toshiba laptop, ToPIC-100 ZV bridge in 'auto' mode.
Does reverting
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/broken-out/gregkh-pci-pci-collect-host-bridge-resources-02.patch
help in your case?
Dominik
Re: ACPI-based PCI resources: PCMCIA bugfix, but resources missing in trees
Quoted 4 lines · Dominik Brodowski
Does reverting
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/broken-out/gregkh-pci-pci-collect-host-bridge-resources-02.patch
help in your case?
CardBus 32-bit NIC appeared with this patch reverted :)
--Grant.
PATCH 1/1 kernel/irq/autoprobe.c: remove an unused variable
In reply to Andrew MortonQuoted 7 lines · Andrew Morton
...
Changes since 2.6.12-mm1:
...
+using-msleep-instead-of-hz.patch
...
cleanup
...
This patch causes the following warning:
<-- snip -->
...
CC kernel/irq/autoprobe.okernel/irq/autoprobe.c: In function `probe_irq_on':kernel/irq/autoprobe.c:30: warning: unused variable `delay'
...
<-- snip -->
This patch removes this no longer used variable.
kernel/irq/autoprobe.c renamed from kernel/irq/autoprobe.c.old +1 -1
@@ -27,7 +27,7 @@*/ unsigned long probe_irq_on (void ) { -unsigned long val, delay; +unsigned long val;irq_desc_t *desc;unsigned int i;
Quoted 2 lines · Andrew Morton
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
Hi Andrew,
Quoted 3 lines
+alsa-maestro3-div-by-zero-fix.patch
Revert an alsa change which appears to cause a divide-by-zero.
I think you can now drop this one.
My "divide error" does not appear in -mm2.
It seems that it is fixed by the following patch:
Quoted 3 lines
+revert-gregkh-pci-pci-assign-unassigned-resources.patch
Revert a bad patch in it
To summarize, everything seems to now work fine on my Compaq Evo N600c laptop. Both breakages I was seeing in -mm1 are now fixed:
* the maestro3 divide error does not appear anymore
* I reported a few days ago that my yenta hang was fixed by pci-yenta-cardbus-fix.patch
Thanks,
Brice
Quoted 7 lines · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/
- A reminder that there is a vger mailing list for tracking patches which are added to -mm. Do
Quoted 8 lines
`echo subscribe mm-commits | mail [email protected]'
- Lots of merges. I'm holding off on the 80-odd pcmcia patches until we get the recent PCI breakage sorted out.
- Big
arch/crisupdate.
This is missing. Is it critical ?
mm/memory.c +1 -1
@@ -1051,7 +1051,7 @@ int remap_pfn_range(struct vm_area_struc {pgd_t *pgd;unsigned long next; -unsigned long end = addr + size; +unsigned long end = addr +PAGE_ALIGN (size);struct mm_struct *mm = vma->vm_mm;int err;
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandriva Linux release 2006.0 (Cooker) for i586
Linux 2.6.12-jam4 (gcc 4.0.1 (4.0.1-0.2mdk for Mandriva Linux release 2006.0))
Quoted 13 lines · J.A. Magallon
This is missing. Is it critical ?
---
2.6.12/mm/memory.c2005-06-17 20:48:29.000000000 +0100
+++linux/mm/memory.c2005-06-21 20:31:42.000000000 +0100
@@ -1051,7 +1051,7 @@ int remap_pfn_range(structvm_area_struc
{
pgd_t*pgd;
unsigned long next;
- unsigned long end = addr + size;
+ unsigned long end = addr +PAGE_ALIGN(size);
structmm_struct*mm =vma->vm_mm;
int err;
That's already in Linus's tree.
Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
In reply to Andrew MortonHi, Andrew.
I am experiencing problems with -mm kernels and my firewire HD. I can use it without any problems with Linus's 2.6.12, but I had problems with both -mm1 and -mm2 (I just compiled -mm2 to see if the problem would go away, but it didn't).
I am using the same .config file for all compiles, except that I wanted to use the -mm tree for some things that I think would be orthogonal to the issue (like using FUSE, for example).
I can't provide more details now, but as soon as I go to work with the machine that presented the problem, I can give you all the details.
Essentially, what happens with -mm kernels that don't happen with Linus's kernel is that the sbp2 module gets loaded, but it seems that the subsystem never gets to actually see the partitions of the HD (I am using a HFS+ formatted disk for transfers of data between Linux and MacOS X).
If others also have the problem, I would like to know about it.
The Firewire controller that I am using is a vanilla VIA card and the HD is a Seagate PATA HD in a Firewire enclosure (it's a ADS Tech DLX-185, if I am not mistaken).
As I said, I can provide further details if wanted/needed.
Thanks for your work, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
(Added linux1394-devel)
Quoted 20 lines · Rogério Brito
Hi, Andrew.
I am experiencing problems with -mm kernels and my firewire HD. I can use it without any problems with Linus's 2.6.12, but I had problems with both -mm1 and -mm2 (I just compiled -mm2 to see if the problem would go away, but it didn't).
I am using the same .config file for all compiles, except that I wanted to use the -mm tree for some things that I think would be orthogonal to the issue (like using FUSE, for example).
I can't provide more details now, but as soon as I go to work with the machine that presented the problem, I can give you all the details.
Essentially, what happens with -mm kernels that don't happen with Linus's kernel is that the sbp2 module gets loaded, but it seems that the subsystem never gets to actually see the partitions of the HD (I am using a HFS+ formatted disk for transfers of data between Linux and MacOS X).
Quoted 9 lines
If others also have the problem, I would like to know about it.
The Firewire controller that I am using is a vanilla VIA card and the HD is a Seagate PATA HD in a Firewire enclosure (it's a ADS Tech DLX-185, if I am not mistaken).
As I said, I can provide further details if wanted/needed.
Could you please generate the dmesg output from 2.6.12 and 2.6.12-mm2 and, if there are any relevant-looking differences, send them?
Also, try:
wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/broken-out/gregkh-pci-pci-collect-host-bridge-resources-02.patch
patch -R -p1 < gregkh-pci-pci-collect-host-bridge-resources-02.patch
Thanks.
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
Quoted 2 lines · Andrew Morton
Could you please generate the dmesg output from 2.6.12 and 2.6.12-mm2 and, if there are any relevant-looking differences, send them?
Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.
Quoted 4 lines
Also, try:
wget (...)
patch -R -p1 < gregkh-pci-pci-collect-host-bridge-resources-02.patch
Ok. I am compiling the kernel right now and will post the results as soon as I am finished.
Quoted 1 line
Thanks.
Thank you very much for your feedback, Rogério.
P.S.: I just noticed right now that the patch listed above changes only arch/i386/pci/acpi.c, but I am not using ACPI. Well, I will proceed anyway.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
Hi, Andrew.
Quoted 1 line · Rogério Brito
Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.
(...)
Quoted 2 lines
P.S.: I just noticed right now that the patch listed above changes onlyarch/i386/pci/acpi.c, but I am not using ACPI. Well, I will proceed anyway.
Well, as I felt before, backing out the patch didn't work. I posted the dmesg of the new compilation on the page above like I did before.
Is there any other patch that I should try to revert?
Thanks, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
In reply to Rogério BritoQuoted 6 lines · Rogério Brito
Quoted 2 lines · Andrew Morton
Could you please generate the dmesg output from 2.6.12 and 2.6.12-mm2 and, if there are any relevant-looking differences, send them?
Ok, I put them both on <http://www.ime.usp.br/~rbrito/bug/>.
Great, here we are:
-ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
+ieee1394: Node added: ID:BUS[0-01:1023] GUID[0050c501e00010e8]
+ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... +ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <[email protected]>
@@ -300,14 +308,6 @@
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: ST316002 Model: 1A Rev: 3.06
- Type: Direct-Access ANSI SCSI revision: 06
-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
-sda: asking for cache data failed
-sda: assuming drive cache: write through
-SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
-sda: asking for cache data failed
-sda: assuming drive cache: write through
- sda: [mac] sda1 sda2 sda3 sda4
-Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
+ Type: Unknown ANSI SCSI revision: 04
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
Could the 1394 guys please suggest what might have caused this?
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
Quoted 1 line
Could the 1394 guys please suggest what might have caused this?
Unless something is in git that isn't in subversion, nothing has really changed in the sbp2 module for 5-6 months.
Doesn't appear to be a problem with the ieee1394 subsystem itself (the cycle master thing isn't all that important), since that would cause not even being able to send/recv packets.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
Quoted 2 lines · Ben Collins
Unless something is in git that isn't in subversion, nothing has really changed in the sbp2 module for 5-6 months.
Is there any other information that I can provide you with that would help track this?
Quoted 3 lines
Doesn't appear to be a problem with the ieee1394 subsystem itself (the cycle master thing isn't all that important), since that would cause not even being able to send/recv packets.
So, could this be a problem with the SCSI layer, then?
Thank you, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels (was: Re: 2.6.12-mm2)
Quoted 6 lines · Rog?rio Brito
Quoted 2 lines · Ben Collins
Unless something is in git that isn't in subversion, nothing has really changed in the sbp2 module for 5-6 months.
Is there any other information that I can provide you with that would help track this?
Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you could.
Quoted 5 lines
Quoted 3 lines
Doesn't appear to be a problem with the ieee1394 subsystem itself (the cycle master thing isn't all that important), since that would cause not even being able to send/recv packets.
So, could this be a problem with the SCSI layer, then?
Doubtful.
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels
Quoted 6 lines · Ben Collins
Quoted 2 lines · Rog?rio Brito
Is there any other information that I can provide you with that would help track this?
Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you could.
Ok, I see that this is getting to be really important now, because I think that Andrew forwarded some patches to Linus and now the Firewire enclosure doesn't seem to work with 2.6.13-rc1 anymore (it works perfectly with vanilla kernel 2.6.12).
The behaviour that I get with 2.6.13-rc1 is the same one that I got with 2.6.12-mm1 or 2.6.12-mm2. :-(
Oh, BTW, I just checked this with another drive, an iPod (2nd Generation) and its partition table is also not read (like what happens with the drive in the Firewire enclosure).
So, I guess that this is another data point that may be useful.
Thank you very much for your help, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Quoted 7 lines · Rog?rio Brito
Quoted 6 lines · Ben Collins
Quoted 2 lines · Rog?rio Brito
Is there any other information that I can provide you with that would help track this?
Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you could.
Where are these patches coming from? Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
Quoted 21 lines
Ok, I see that this is getting to be really important now, because I think that Andrew forwarded some patches to Linus and now the Firewire enclosure doesn't seem to work with 2.6.13-rc1 anymore (it works perfectly with vanilla kernel 2.6.12).
The behaviour that I get with 2.6.13-rc1 is the same one that I got with 2.6.12-mm1 or 2.6.12-mm2. :-(
Oh, BTW, I just checked this with another drive, an iPod (2nd Generation) and its partition table is also not read (like what happens with the drive in the Firewire enclosure).
So, I guess that this is another data point that may be useful.
Thank you very much for your help, Rog?rio.
Signature · 3 lines
Rog?rio Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels
Quoted 11 lines · Ben Collins
Quoted 7 lines · Rog?rio Brito
Quoted 6 lines · Ben Collins
Quoted 2 lines · Rog?rio Brito
Is there any other information that I can provide you with that would help track this?
Diff git2's ieee1394 directory and the SVN repo from linux1394.org if you could.
Where are these patches coming from? Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
I don't know where the patches are coming from. I have just checked out the trunk version of the subversion tree from linux1394.org. I will diff it against the Linux tree that I have here.
Humm, I have just diffed both trees and there is a fair amount of changes between both versions (i.e., between Linux 2.6.13-rc1 and the trunk tree from linux1394.org).
The diff (in this order) is at http://www.ime.usp.br/~rbrito/bug/, if you can comment on it.
I can provide any other information that is needed. Just let me know what is desired.
Thank you very much, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels (and vanilla 2.6.13-rc1)
In reply to Ben CollinsQuoted 1 line · Ben Collins
Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
I am doing this right now. I will let you know the resuts as soon as I get the kernel compiled.
Thanks, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
In reply to Ben CollinsQuoted 1 line · Ben Collins
Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
Here is what I get when I try to substitute 2.6.13-rc1 with linux1394 trunk's tree:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (...)
CC [M] drivers/block/loop.o CC [M] drivers/block/pktcdvd.o CC [M] drivers/block/cryptoloop.o CC [M] drivers/char/agp/intel-agp.o CC [M] drivers/ieee1394/ieee1394_core.o
drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread':drivers/ieee1394/ieee1394_core.c:1048: error: too many arguments to function refrigerator' drivers/ieee1394/ieee1394_core.c: In function ieee1394_init':drivers/ieee1394/ieee1394_core.c:1127: warning: implicit declaration of function `class_simple_create' drivers/ieee1394/ieee1394_core.c:1127: warning: assignment makes pointer from integer without a cast drivers/ieee1394/ieee1394_core.c:1165: warning: implicit declaration of function `class_simple_destroy' make[3]: *** [drivers/ieee1394/ieee1394_core.o] Error 1
make[2]: *** [drivers/ieee1394] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/local/media/progs/linux/linux'
make: *** [stamp-build] Error 2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Thanks, Rogério Brito.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Most of this is class_simple changes.
However, there is a huge set of changes to sbp2. One thing that sticks out is the entire sbp2_check_sbp2_command() function being ripped out. There's some changes related to TYPE_SDAD devices (where did this come from?).
Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
I'll see if I can figure out why our tree and kernel tree have gotten so far out of whack and how such huge changes that don't seem to fix anything (like the large changes to sbp2) have gotten into the kernel proper without being tested. Most of the sbp2 changes seem to be a new feature rather than fixing minor or even major bugs.
Quoted 31 lines · Rog?rio Brito
Quoted 1 line · Ben Collins
Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
Here is what I get when I try to substitute 2.6.13-rc1 with linux1394 trunk's tree:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (...)CC [M] drivers/block/loop.o CC [M] drivers/block/pktcdvd.o CC [M] drivers/block/cryptoloop.o CC [M] drivers/char/agp/intel-agp.o CC [M] drivers/ieee1394/ieee1394_core.o
drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread':drivers/ieee1394/ieee1394_core.c:1048: error: too many arguments to functionrefrigerator' drivers/ieee1394/ieee1394_core.c: In functionieee1394_init':drivers/ieee1394/ieee1394_core.c:1127: warning: implicit declaration of function `class_simple_create'drivers/ieee1394/ieee1394_core.c:1127: warning: assignment makes pointer from integer without a castdrivers/ieee1394/ieee1394_core.c:1165: warning: implicit declaration of function `class_simple_destroy' make[3]: *** [drivers/ieee1394/ieee1394_core.o] Error 1
make[2]: *** [drivers/ieee1394] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/local/media/progs/linux/linux'
make: *** [stamp-build] Error 2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Thanks, Rog?rio Brito.
Signature · 3 lines
Rog?rio Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels
Quoted 5 lines · Ben Collins
Most of this is
class_simplechanges.However, there is a huge set of changes to sbp2. One thing that sticks out is the entire
sbp2_check_sbp2_command()function being ripped out. There's some changes related toTYPE_SDADdevices (where did this come from?).
This is the TYPE_RBC cache fixes patch by Al Viro. That discussion went on for a while with additional changes suggested, and I did not know the resolution. Now we do. :-)
Quoted 4 lines
Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
I'll see if I can figure out why our tree and kernel tree have gotten so far out of whack and how such huge changes that don't seem to fix anything
Obviously, much of the diff Rogerio produced (not in history below) shows changes in our repo not yet submitted to kernel.
Quoted 37 lines
(like the large changes to sbp2) have gotten into the kernel proper without being tested. Most of the sbp2 changes seem to be a new feature rather than fixing minor or even major bugs.
Quoted 31 lines · Rog?rio Brito
Quoted 1 line · Ben Collins
Also, have you tried using 2.6.13-rc1 using linux1394.org's subversion tree?
Here is what I get when I try to substitute 2.6.13-rc1 with linux1394 trunk's tree:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (...)CC [M] drivers/block/loop.o CC [M] drivers/block/pktcdvd.o CC [M] drivers/block/cryptoloop.o CC [M] drivers/char/agp/intel-agp.o CC [M] drivers/ieee1394/ieee1394_core.o
drivers/ieee1394/ieee1394_core.c: In function `hpsbpkt_thread':drivers/ieee1394/ieee1394_core.c:1048: error: too many arguments to functionrefrigerator' drivers/ieee1394/ieee1394_core.c: In functionieee1394_init':drivers/ieee1394/ieee1394_core.c:1127: warning: implicit declaration of function `class_simple_create'drivers/ieee1394/ieee1394_core.c:1127: warning: assignment makes pointer from integer without a castdrivers/ieee1394/ieee1394_core.c:1165: warning: implicit declaration of function `class_simple_destroy' make[3]: *** [drivers/ieee1394/ieee1394_core.o] Error 1
make[2]: *** [drivers/ieee1394] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/local/media/progs/linux/linux'
make: *** [stamp-build] Error 2
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Thanks, Rog?rio Brito.
Signature · 3 lines
Rog?rio Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Quoted 2 lines · Dan Dennedy
Obviously, much of the diff Rogerio produced shows changes in our repo not yet submitted to kernel.
It is actually a mixture of that and of 'external' changes which were not yet merged back into the Linux1394 repo.
Signature · 3 lines
Stefan Richter -=====-=-=-= -=== ----= http://arcgraph.de/sr/
Re: Problems with Firewire and -mm kernels
In reply to Ben CollinsQuoted 3 lines · Ben Collins
However, there is a huge set of changes to sbp2. One thing that sticks out is the entire
sbp2_check_sbp2_command()function being ripped out. There's some changes related toTYPE_SDADdevices (where did this come from?).
The TYPE_SDAD -> TYPE_RBC changes come from the scsi maintainers. Here is the related discussion from May: 'TYPE_RBC cache fixes (sbp2.c affected)', http://marc.theaimsgroup.com/?t=111620896500001
(Back then I wanted to test their patch but did not find the time.)
Signature · 3 lines
Stefan Richter -=====-=-=-= -=== ----= http://arcgraph.de/sr/
Re: Problems with Firewire and -mm kernels
In reply to Ben CollinsQuoted 1 line · Ben Collins
Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
Ok, I did that and it worked fine, thanks! I'm trying to upload the resulting dmesg so that you can see yourself, but it seems that my University's site isn't working for some reason. :-(
Oh, I got one warning when I was compiling sbp2.c (it was something like an invalid initialization around line 27xx--yes, yes, I know that this doesn't help much, but I don't have the log of the compilation here).
Quoted 5 lines
I'll see if I can figure out why our tree and kernel tree have gotten so far out of whack and how such huge changes that don't seem to fix anything (like the large changes to sbp2) have gotten into the kernel proper without being tested. Most of the sbp2 changes seem to be a new feature rather than fixing minor or even major bugs.
Yes, it would help a lot if the fixes were included in 2.6.13 (final).
Thank you very much again, Rogério Brito.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Quoted 10 lines · Rog?rio Brito
Quoted 1 line · Ben Collins
Try reverting just the sbp2.[ch] changes from the 2.6.13-rc1 tree.
Ok, I did that and it worked fine, thanks! I'm trying to upload the resulting dmesg so that you can see yourself, but it seems that my University's site isn't working for some reason. :-(
Oh, I got one warning when I was compiling
sbp2.c(it was something like an invalid initialization around line 27xx--yes, yes, I know that this doesn't help much, but I don't have the log of the compilation here).
Ok, so the TYPE_SDAD/TYPE_RBC changes did affect sbp2. I think the changes look a little much for what it was trying to accomplish (moving code around between functions and changing logic paths is a little much when no one tests it).
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels
In reply to Andrew MortonReview
Quoted 5 lines · Andrew Morton
(quoted diff) +3
-1-ieee1394: Node added: ID:BUS[0-00:1023] GUID[0050c501e00010e8] +ieee1394: Node added: ID:BUS[0-01:1023] GUID[0050c501e00010e8] +ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... +ieee1394: Node changed: 0-01:1023 -> 0-00:1023 ieee1394: Node changed: 0-00:1023 -> 0-01:1023
The IDs are assigned to nodes everytime they are attached to the bus in a random order. It is a pure hardware thing; I cannot imagine any influnce of the kernel to this procedure.
If the node with the highest ID does not fulfill certain criteria, Linux tries to get the highest ID moved to the local node. This function is unrelated to SBP-2 (it is necessary to let streaming devices like cameras work) but it has been observed that it disturbs a few SBP-2 devices. But again, I don't see how -mm and the stock kernel should differ to that respect.
You could load ieee1394 with a new parameter that supresses the "Root node is not cycle master capable..." routine:
# modprobe ieee1394 disable_irm=1 before ohci1394 and the other 1394 related drivers are loaded.
Quoted 6 lines
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <[email protected]>(quoted diff) +0
-0@@ -300,14 +308,6 @@ ieee1394: sbp2: Logged into SBP-2 device ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048] Vendor: ST316002 Model: 1A Rev: 3.06
Review line 311
Quoted 10 lines
(quoted diff) +1
-9- Type: Direct-Access ANSI SCSI revision: 06 -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) -sda: asking for cache data failed -sda: assuming drive cache: write through -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) -sda: asking for cache data failed -sda: assuming drive cache: write through - sda: [mac] sda1 sda2 sda3 sda4 -Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 + Type: Unknown ANSI SCSI revision: 04
There was a discussion in May about discovery of devices which implement the RBC command set: http://marc.theaimsgroup.com/?t=111620896500001 I am not sure if the discussed change went into one or both of the kernels in question.
Review line 313
Quoted 2 lines
(quoted diff) +0
-0ieee1394: Node changed: 0-01:1023 -> 0-00:1023 ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]
What caused these two messages? Did you disconnect the drive at this point?
Signature · 3 lines
Stefan Richter -=====-=-=-= -==- ===-- http://arcgraph.de/sr/
Re: Problems with Firewire and -mm kernels
Quoted 5 lines · Stefan Richter
Quoted 3 lines
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]What caused these two messages? Did you disconnect the drive at this point?
No, there is no device plugged into the machine.
Maybe the G5 has some internal 1394 device? It would be news to me if so.
Re: Problems with Firewire and -mm kernels
Quoted 9 lines · Andrew Morton
Quoted 6 lines · Stefan Richter
Quoted 3 lines
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]What caused these two messages? Did you disconnect the drive at this point?
No, there is no device plugged into the machine.
Right, at that time I had already disconnected the drive.
Quoted 1 line
Maybe the G5 has some internal 1394 device? It would be news to me if so.
Heh, I don't have the money for a G5. :-) I'm using this on a vanilla x86 with a Duron 1.1GHz (which I recently upgraded from a Duron 600MHz).
Perhaps I should provide more information regarding my system? If yes, please let me know what and I will do my best.
Thanks, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Quoted 4 lines
Quoted 1 line
Maybe the G5 has some internal 1394 device? It would be news to me if so.
Heh, I don't have the money for a G5. :-) I'm using this on a vanilla x86 with a Duron 1.1GHz (which I recently upgraded from a Duron 600MHz).
I think Andrew got two of his 1394 threads mixed up here in that last response :)
Signature · 4 lines
Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/
Re: Problems with Firewire and -mm kernels
In reply to Andrew MortonQuoted 10 lines · Andrew Morton
Quoted 5 lines · Stefan Richter
Quoted 3 lines
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]What caused these two messages? Did you disconnect the drive at this point?
No, there is no device plugged into the machine.
Maybe the G5 has some internal 1394 device? It would be news to me if so.
Well, I would assume the Macs play some trick with the internal Firewire and IDE/SCSI channels to allow the internal hard disk to come up as firewire hard disks for other Macs when in Target mode. So maybe that's the result of this?
Signature · 7 lines
Giuseppe "Oblomov" Bilotta
"Da grande lotterò per la pace"
"A me me la compra il mio babbo"
(Altan)
("When I grow up, I will fight for peace"
"I'll have my daddy buy it for me")Re: Problems with Firewire and -mm kernels
In reply to Stefan RichterQuoted 2 lines · Stefan Richter
But again, I don't see how -mm and the stock kernel should differ to that respect.
Well, I can only say that this problem is 100% reproducible with my enclosure.
Perhaps more data is needed here? The 2.6.12 kernel is able to see the drive without any problems while the -mm kernels aren't. I can provide anything that you guys want.
Right now, I am using a stock/vanilla kernel, for using the drive.
Quoted 4 lines
You could load ieee1394 with a new parameter that supresses the "Root node is not cycle master capable..." routine:
# modprobe ieee1394 disable_irm=1 before ohci1394 and the other 1394 related drivers are loaded.
Ok, I'll disable hotplug, udev etc and try to boot into single user mode for that as soon as I wake up (I'm going to bed right now---had a lot of work done for a day).
Quoted 5 lines
Quoted 2 lines
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]What caused these two messages? Did you disconnect the drive at this point?
Yes, I did. In both cases, just to see if any messages issued to dmesg were different when unplugging the drive.
If you have other ideas or if any extra information is necessary, please, let me know and I'll do my best to provide what you need.
Thank you all for the interest, Rogério.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
Re: Problems with Firewire and -mm kernels
Quoted 10 lines · Rogério Brito
Quoted 2 lines · Stefan Richter
But again, I don't see how -mm and the stock kernel should differ to that respect.
Well, I can only say that this problem is 100% reproducible with my enclosure.
Perhaps more data is needed here? The 2.6.12 kernel is able to see the drive without any problems while the -mm kernels aren't. I can provide anything that you guys want.
What we know is:
- With -mm, your machine started to require the switching of phy IDs for a proper cycle master.
- With -mm, the device formerly sensed by scsi_mod's probe as "Direct-Access" device + SCSI rev 06 is allegedly of "Unknown" type + SCSI rev 04 now. Vendor and model are still recognized though.
So what we don't know at the moment is:
- What did change to make the formerly "unlikely to happen" FireWire bus reset "extremely likely to happen" now? (That is how I interpret the ratio of 0% to 100% which you observed.)
- Does this reset infuence how the device answers to scsi inquiries? So far there were only reports on the linux1394 mailinglists indicating that with this reset, devices respond differently to config ROM queries from the ieee1394 driver. This is way before sbp2 and scsi_mod get to know about the device.
My current uneducated guess is that the FireWire bus reset and the SCSI probing problem are actually unrelated. The cause for the latter problem might be 2.6.12-mm2/broken-out/git-scsi-block.patch. At least that is what I think after a look through the -mm2 patch collection.
Quoted 7 lines
Quoted 3 lines
You could load ieee1394 with a new parameter that supresses the "Root node is not cycle master capable..." routine:
# modprobe ieee1394 disable_irm=1 before ohci1394 and the other 1394 related drivers are loaded.Ok, I'll disable hotplug, udev etc and try to boot into single user mode for that as soon as I wake up (I'm going to bed right now---had a lot of work done for a day).
You do not need to go through all this. Unload all 1394 drivers (although this may fail sometimes when scsi does not let go of sbp2), then reload ieee1394 with the parameter, then ohci1394. No need to go into another runlevel or to mess around with hotplug or udev.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0050c501e00010e8]What caused these two messages? Did you disconnect the drive at this point?
Yes, I did. In both cases, just to see if any messages issued to dmesg were different when unplugging the drive.
Then these two messages are OK.
Signature · 3 lines
Stefan Richter -=====-=-=-= -==- ===-- http://arcgraph.de/sr/
Re: Problems with Firewire and -mm kernels
In reply to Stefan RichterQuoted 6 lines · Stefan Richter
If the node with the highest ID does not fulfill certain criteria, Linux tries to get the highest ID moved to the local node. This function is unrelated to SBP-2 (it is necessary to let streaming devices like cameras work) but it has been observed that it disturbs a few SBP-2 devices. But again, I don't see how -mm and the stock kernel should differ to that respect.
Well, my observation is that they differ. Well, up to kernel 2.6.13-rc1. This latest kernel shows the same behaviour that -mm showed, unfortunately.
Quoted 4 lines
You could load ieee1394 with a new parameter that supresses the "Root node is not cycle master capable..." routine:
# modprobe ieee1394 disable_irm=1 before ohci1394 and the other 1394 related drivers are loaded.
Now *this* made things work! I have put another dmesg log on my homepage at
http://www.ime.usp.br/~rbrito/bug/ (see the 3rd-try log). This made things work and I could mount the device.
I had to disable hotplug and udev, since trying to unload the Firewire modules made my machine hang (I think that it was trying to unload ohci1394 that made my machine hang).
So, does this ring any bell? Can I provide extra information?
I am keeping the following diff just for reference's sake:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Quoted 6 lines
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <[email protected]>(quoted diff) +0
-0@@ -300,14 +308,6 @@ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: ST316002 Model: 1A Rev: 3.06
Review
Quoted 10 lines
(quoted diff) +1
-9- Type: Direct-Access ANSI SCSI revision: 06 -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) -sda: asking for cache data failed -sda: assuming drive cache: write through -SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) -sda: asking for cache data failed -sda: assuming drive cache: write through - sda: [mac] sda1 sda2 sda3 sda4 -Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 + Type: Unknown ANSI SCSI revision: 04
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Thanks for all your kind responses, Rogério Brito.
Signature · 3 lines
Rogério Brito : [email protected] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/
[sparc32] Kconfig fixups (was Re: 2.6.12-mm2)
In reply to Andrew MortonQuoted 1 line · Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm2/
Something reverted most of the arch/sparc/Kconfig changes, leaving arch/sparc/ unconfigurable. This patch re-removes the parts made redundant by drivers/Kconfig in addition to a mysterious, spurious second instance of source "mm/Kconfig". cvs strikes again?
arch/sparc/Kconfig +0 -56
@@ -270,66 +270,10 @@ source "drivers/Kconfig" -config PRINTER - tristate "Parallel printer support" - depends on PARPORT - ---help--- - If you intend to attach a printer to the parallel port of your Linux - box (as opposed to using a serial printer; if the connector at the - printer has 9 or 25 holes ["female"], then it's serial), say Y. - Also read the Printing-HOWTO, available from - <http://www.tldp.org/docs.html#howto>. - - It is possible to share one parallel port among several devices - (e.g. printer and ZIP drive) and it is safe to compile the - corresponding drivers into the kernel. If you want to compile this - driver as a module however, choose M here and read - <file:Documentation/parport.txt>. The module will be called lp. - - If you have several parallel ports, you can specify which ports to - use with the "lp" kernel command line option. (Try "man bootparam" - or see the documentation of your boot loader (silo) about how to pass - options to the kernel at boot time.) The syntax of the "lp" command - line option can be found in <file:drivers/char/lp.c>. - - If you have more than 8 printers, you need to increase the LP_NO - macro in lp.c and the PARPORT_MAX macro in parport.h. - -source "mm/Kconfig" - -endmenu - -source "drivers/base/Kconfig" - -source "drivers/video/Kconfig" - -source "drivers/mtd/Kconfig" - -source "drivers/serial/Kconfig" - if !SUN4 source "drivers/sbus/char/Kconfig" endif -source "drivers/block/Kconfig" - -# Don't frighten a common SBus user -if PCI - -source "drivers/ide/Kconfig" - -endif - -source "drivers/isdn/Kconfig" - -source "drivers/scsi/Kconfig" - -source "drivers/fc4/Kconfig" - -source "drivers/md/Kconfig" - -source "net/Kconfig" - # This one must be before the filesystem configs. -DaveM menu "Unix98 PTY support"