From 7a6651c730ed177ef31acef983d05f69cea8c4b0 Mon Sep 17 00:00:00 2001 From: Jochen Maes Date: Sun, 29 Mar 2015 17:23:00 +0200 Subject: [PATCH] Update linux-mm-1.md Typos --- mm/linux-mm-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/linux-mm-1.md b/mm/linux-mm-1.md index 1773e4d..d98038a 100644 --- a/mm/linux-mm-1.md +++ b/mm/linux-mm-1.md @@ -28,7 +28,7 @@ struct memblock { }; ``` -This structure contains five fields. First is `bottom_up` which allows to allocate memory in bottom-up mode when it is `true`. Next field is `current_limit`. This field describes the limit size of the memory block. The next three feilds describes the type of the memory block. It can be: reserved, memory andphysical memory if `CONFIG_HAVE_MEMBLOCK_PHYS_MAP` configuration option is enabled. Now we met yet another data structure - `memblock_type`. Let's look on its definition: +This structure contains five fields. First is `bottom_up` which allows to allocate memory in bottom-up mode when it is `true`. Next field is `current_limit`. This field describes the limit size of the memory block. The next three fields describes the type of the memory block. It can be: reserved, memory and physical memory if `CONFIG_HAVE_MEMBLOCK_PHYS_MAP` configuration option is enabled. Now we met yet another data structure - `memblock_type`. Let's look on its definition: ```C struct memblock_type {