diff options
| author | Mike Rapoport <rppt@linux.vnet.ibm.com> | 2018-03-21 22:22:47 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2018-04-16 23:18:15 +0300 |
| commit | ad56b738c5dd223a2f66685830f82194025a6138 (patch) | |
| tree | 3994f40f1f93aec279d0b5c9117c0085a9f9ab03 /Documentation/dev-tools | |
| parent | 3406bb5c64a091ad887c3fb339ad88e9e88ef938 (diff) | |
| download | linux-ad56b738c5dd223a2f66685830f82194025a6138.tar.xz | |
docs/vm: rename documentation files to .rst
Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/dev-tools')
| -rw-r--r-- | Documentation/dev-tools/kasan.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/dev-tools/kasan.rst b/Documentation/dev-tools/kasan.rst index f7a18f274357..aabc8738b3d8 100644 --- a/Documentation/dev-tools/kasan.rst +++ b/Documentation/dev-tools/kasan.rst @@ -120,7 +120,7 @@ A typical out of bounds access report looks like this:: The header of the report discribe what kind of bug happened and what kind of access caused it. It's followed by the description of the accessed slub object -(see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and +(see 'SLUB Debug output' section in Documentation/vm/slub.rst for details) and the description of the accessed memory page. In the last section the report shows memory state around the accessed address. |