Andrew Morton <akpm@xxxxxxxx> wrote: > > Of course it doesn't always work out that simply ;) > > In this case it's not clear that a tsort will work out right. I'll take a > look. Well it wasn't completely clean, and I forgot to rename the patches, but this is how the tsort came out: 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-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 So we can later work out which of these to fold into which other ones. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
