diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2024-05-27 21:37:18 -0700 |
|---|---|---|
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2024-05-27 21:37:18 -0700 |
| commit | 6f47c7ae8c7afaf9ad291d39f0d3974f191a7946 (patch) | |
| tree | 74ce89b352cb8096e6a94ddc8597274d3e2d53ce /Documentation/mm/hwpoison.rst | |
| parent | 832f54c9ccd3a3f32d1db905462d3c58b4df52bd (diff) | |
| parent | a38297e3fb012ddfa7ce0321a7e5a8daeb1872b6 (diff) | |
Merge tag 'v6.9' into next
Sync up with the mainline to bring in the new cleanup API.
Diffstat (limited to 'Documentation/mm/hwpoison.rst')
| -rw-r--r-- | Documentation/mm/hwpoison.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/mm/hwpoison.rst b/Documentation/mm/hwpoison.rst index ba48a441feed..483b72aa7c11 100644 --- a/Documentation/mm/hwpoison.rst +++ b/Documentation/mm/hwpoison.rst @@ -48,7 +48,7 @@ of applications. KVM support requires a recent qemu-kvm release. For the KVM use there was need for a new signal type so that KVM can inject the machine check into the guest with the proper address. This in theory allows other applications to handle -memory failures too. The expection is that near all applications +memory failures too. The expectation is that most applications won't do that, but some very specialized ones might. Failure recovery modes |