diff for duplicates of <1109715340.5680.34.camel@gaston> diff --git a/a/1.txt b/N1/1.txt index 5851e6b..e5e057b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -20,7 +20,7 @@ On IBM pSeries machine (and I'm trying to figure out an API to deal with that generically for drivers), upon a PCI error (either MMIO error or DMA error), the slot is put in isolation automatically. -From this point, we can instruct the firmware to 1) re-enable MMIO, 2) +>From this point, we can instruct the firmware to 1) re-enable MMIO, 2) re-enable DMA, 3) proceed to a slot reset and re-enable MMIO & DMA. That allows all sort of recovery strategies. However, obviously, not all diff --git a/a/content_digest b/N1/content_digest index 7ad8f79..654e21f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,7 @@ "ref\042249A44.4020507@pobox.com\0" "From\0Benjamin Herrenschmidt <benh@kernel.crashing.org>\0" "Subject\0Re: [PATCH/RFC] I/O-check interface for driver's error handling\0" - "Date\0Tue, 01 Mar 2005 22:15:40 +0000\0" + "Date\0Wed, 02 Mar 2005 09:15:40 +1100\0" "To\0Jeff Garzik <jgarzik@pobox.com>\0" "Cc\0Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>" Linux Kernel list <linux-kernel@vger.kernel.org> @@ -36,7 +36,7 @@ "that generically for drivers), upon a PCI error (either MMIO error or\n" "DMA error), the slot is put in isolation automatically.\n" "\n" - "From this point, we can instruct the firmware to 1) re-enable MMIO, 2)\n" + ">From this point, we can instruct the firmware to 1) re-enable MMIO, 2)\n" "re-enable DMA, 3) proceed to a slot reset and re-enable MMIO & DMA.\n" "\n" "That allows all sort of recovery strategies. However, obviously, not all\n" @@ -71,4 +71,4 @@ "\n" Ben. -9754bfbb5873fd4ac2835169775bd21ebcd3e93b0b9a9448401658faf32df6ee +961e34f9d7499d9f122eb024e750a07ce039411712014febb33d59f13489a87b
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.