{"push_id":819323620,"size":61,"distinct_size":61,"ref":"refs/heads/TW502","head":"9ce646af6584789146e4a7078025e0257c326c3b","before":"50146b5d0ad599f1e173ec048969e349915d420a","commits":[{"sha":"ac87023be8dce774b9acb53878b7e14610aa8ca0","author":{"email":"dab1ac482cbf0c585f9ac2c32308f0f07e56569c@outlook.com","name":"Tkkg1994"},"message":"Revert \"ARM: constify machine_desc structure uses\"\n\nThis reverts commit 50146b5d0ad599f1e173ec048969e349915d420a.","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/ac87023be8dce774b9acb53878b7e14610aa8ca0"},{"sha":"8e176160ab88acbfe1d6de7290503709a825e621","author":{"email":"e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","name":"Laura Abbott"},"message":"arm: Get rid of meminfo\n\nmemblock is now fully integrated into the kernel and is the prefered\nmethod for tracking memory. Rather than reinvent the wheel with\nmeminfo, migrate to using memblock directly instead of meminfo as\nan intermediate.\n\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tarch/arm/mm/init.c","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/8e176160ab88acbfe1d6de7290503709a825e621"},{"sha":"9c6db96534d4902c2f60c0d1939485a84829dcb3","author":{"email":"f6aa0246ff943bfa8602cdf60d40c481b38ed232@arm.linux.org.uk","name":"Russell King"},"message":"ARM: constify machine_desc structure uses\n\nstruct machine_desc records are defined everywhere as a 'const'\nstructure, but unfortuantely it loses its const-ness through the use of\nlinker magic - the symbols which surround the section are not declared\nconst so it becomes possible not to use 'const' for pointers to these\nconst structures.\n\nLet's fix this oversight - all pointers to these structures should be\nmarked const too.\n\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\n[joonwoop@codeaurora.org: fixed trivial merge conflict. constify some\n more code to avoid warning.]\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tarch/arm/include/asm/prom.h\n\tarch/arm/kernel/setup.c","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/9c6db96534d4902c2f60c0d1939485a84829dcb3"},{"sha":"09af7076517db102b627ff5699f8dd0efb9b2b0e","author":{"email":"a62d066fcbab732c2ebe9cb02e2d29694a514faf@codeaurora.org","name":"Shiraz Hashim"},"message":"arm: mm: fix and cleanup function to print vmalloc info\n\nprint_vmalloc_lowmem_info incorrectly uses __va macro for\nhighmem addresses to print vmalloc and lowmem region\ninformation. This results in incorrect prints particularly\nfor platforms with higher DDR sizes where the __va wraps\nand gives incorrect virtual addresses. Fix this and\nsimplify whole function.\n\nSigned-off-by: Shiraz Hashim <shashim@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/09af7076517db102b627ff5699f8dd0efb9b2b0e"},{"sha":"1ada5ee8753675234aade7b510a7daadaa9df67b","author":{"email":"e7b4910f4742918f5926c991d8a2cd122ac7e295@codeaurora.org","name":"Laura Abbott"},"message":"mm/memblock: Add for_each_memblock_rev\n\nIt's useful to be able to go through memblock in descending order of\naddresses. Add a macro to define this.\n\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/1ada5ee8753675234aade7b510a7daadaa9df67b"},{"sha":"57cc658b0c24d3a9765ea3720e4a6a9ab9c719f0","author":{"email":"bb6c8cfe7699e0f11d1bee88022eb563a5f8e881@lge.com","name":"Joonsoo Kim"},"message":"topology: add support for node_to_mem_node() to determine the fallback node\n\nAnton noticed (http://www.spinics.net/lists/linux-mm/msg67489.html) that\non ppc LPARs with memoryless nodes, a large amount of memory was consumed\nby slabs and was marked unreclaimable.  He tracked it down to slab\ndeactivations in the SLUB core when we allocate remotely, leading to poor\nefficiency always when memoryless nodes are present.\n\nAfter much discussion, Joonsoo provided a few patches that help\nsignificantly.  They don't resolve the problem altogether:\n\n - memory hotplug still needs testing, that is when a memoryless node\n   becomes memory-ful, we want to dtrt\n - there are other reasons for going off-node than memoryless nodes,\n   e.g., fully exhausted local nodes\n\nNeither case is resolved with this series, but I don't think that should\nblock their acceptance, as they can be explored/resolved with follow-on\npatches.\n\nThe series consists of:\n\n[1/3] topology: add support for node_to_mem_node() to determine the\n      fallback node\n\n[2/3] slub: fallback to node_to_mem_node() node if allocating on\n      memoryless node\n\n      - Joonsoo's patches to cache the nearest node with memory for each\n        NUMA node\n\n[3/3] Partial revert of 81c98869faa5 (\"\"kthread: ensure locality of\n      task_struct allocations\")\n\n - At Tejun's request, keep the knowledge of memoryless node fallback\n   to the allocator core.\n\nThis patch (of 3):\n\nWe need to determine the fallback node in slub allocator if the allocation\ntarget node is memoryless node.  Without it, the SLUB wrongly select the\nnode which has no memory and can't use a partial slab, because of node\nmismatch.  Introduced function, node_to_mem_node(X), will return a node Y\nwith memory that has the nearest distance.  If X is memoryless node, it\nwill return nearest distance node, but, if X is normal node, it will\nreturn itself.\n\nWe will use this function in following patch to determine the fallback\nnode.\n\nSigned-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nSigned-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>\nCc: David Rientjes <rientjes@google.com>\nCc: Han Pingtian <hanpt@linux.vnet.ibm.com>\nCc: Pekka Enberg <penberg@kernel.org>\nCc: Paul Mackerras <paulus@samba.org>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Michael Ellerman <mpe@ellerman.id.au>\nCc: Anton Blanchard <anton@samba.org>\nCc: Christoph Lameter <cl@linux.com>\nCc: Wanpeng Li <liwanp@linux.vnet.ibm.com>\nCc: Tejun Heo <tj@kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/57cc658b0c24d3a9765ea3720e4a6a9ab9c719f0"},{"sha":"1862ef89e88035804c4ffe39760fd7b5d801edd9","author":{"email":"a683964d4489dfcd1de21d1566170b1d560c877b@asianux.com","name":"Chen Gang"},"message":"mm/page_alloc.c: use '__paginginit' instead of '__init'\n\nset_pageblock_order() may be called when memory hotplug, so need use\n'__paginginit' instead of '__init'.\n\nThe related warning:\n\n  The function __meminit .free_area_init_node() references\n  a function __init .set_pageblock_order().\n  If .set_pageblock_order is only used by .free_area_init_node then\n  annotate .set_pageblock_order with a matching annotation.\n\nSigned-off-by: Chen Gang <gang.chen@asianux.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Laura Abbott <lauraa@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/1862ef89e88035804c4ffe39760fd7b5d801edd9"},{"sha":"f65f31899d12bc52dea03d7bb8c8e7ba0eeb1a70","author":{"email":"bb6c8cfe7699e0f11d1bee88022eb563a5f8e881@lge.com","name":"Joonsoo Kim"},"message":"mm/page_alloc: fix incorrect isolation behavior by rechecking migratetype\n\nThere are two paths to reach core free function of buddy allocator,\n__free_one_page(), one is free_one_page()->__free_one_page() and the\nother is free_hot_cold_page()->free_pcppages_bulk()->__free_one_page().\nEach paths has race condition causing serious problems. At first, this\npatch is focused on first type of freepath. And then, following patch\nwill solve the problem in second type of freepath.\n\nIn the first type of freepath, we got migratetype of freeing page without\nholding the zone lock, so it could be racy. There are two cases of this\nrace.\n\n1. pages are added to isolate buddy list after restoring orignal\nmigratetype\n\nCPU1                                   CPU2\n\nget migratetype => return MIGRATE_ISOLATE\ncall free_one_page() with MIGRATE_ISOLATE\n\n\t\t\t\tgrab the zone lock\n\t\t\t\tunisolate pageblock\n\t\t\t\trelease the zone lock\n\ngrab the zone lock\ncall __free_one_page() with MIGRATE_ISOLATE\nfreepage go into isolate buddy list,\nalthough pageblock is already unisolated\n\nThis may cause two problems. One is that we can't use this page anymore\nuntil next isolation attempt of this pageblock, because freepage is on\nisolate buddy list. The other is that freepage accouting could be wrong\ndue to merging between different buddy list. Freepages on isolate buddy\nlist aren't counted as freepage, but ones on normal buddy list are counted\nas freepage. If merge happens, buddy freepage on normal buddy list is\ninevitably moved to isolate buddy list without any consideration of\nfreepage accouting so it could be incorrect.\n\n2. pages are added to normal buddy list while pageblock is isolated.\nIt is similar with above case.\n\nThis also may cause two problems. One is that we can't keep these\nfreepages from being allocated. Although this pageblock is isolated,\nfreepage would be added to normal buddy list so that it could be\nallocated without any restriction. And the other problem is same as\ncase 1, that it, incorrect freepage accouting.\n\nThis race condition would be prevented by checking migratetype again\nwith holding the zone lock. Because it is somewhat heavy operation\nand it isn't needed in common case, we want to avoid rechecking as much\nas possible. So this patch introduce new variable, nr_isolate_pageblock\nin struct zone to check if there is isolated pageblock.\nWith this, we can avoid to re-check migratetype in common case and do\nit only if there is isolated pageblock or migratetype is MIGRATE_ISOLATE.\nThis solve above mentioned problems.\n\nCc: <stable@vger.kernel.org>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Michal Nazarewicz <mina86@mina86.com>\nAcked-by: Vlastimil Babka <vbabka@suse.cz>\nSigned-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nPatch-mainline: linux-kernel @ 10/31/2014 16:25:27\n[vinmenon@codeaurora.org: get_pfnblock_migratetype replaced by\nget_pageblock_migratetype plus fixed merge conflicts]\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/f65f31899d12bc52dea03d7bb8c8e7ba0eeb1a70"},{"sha":"879a0fb672459d62e123c5fc391b57be33c193f9","author":{"email":"bb6c8cfe7699e0f11d1bee88022eb563a5f8e881@lge.com","name":"Joonsoo Kim"},"message":"mm/page_alloc: add freepage on isolate pageblock to correct buddy list\n\nIn free_pcppages_bulk(), we use cached migratetype of freepage\nto determine type of buddy list where freepage will be added.\nThis information is stored when freepage is added to pcp list, so\nif isolation of pageblock of this freepage begins after storing,\nthis cached information could be stale. In other words, it has\noriginal migratetype rather than MIGRATE_ISOLATE.\n\nThere are two problems caused by this stale information. One is that\nwe can't keep these freepages from being allocated. Although this\npageblock is isolated, freepage will be added to normal buddy list\nso that it could be allocated without any restriction. And the other\nproblem is incorrect freepage accounting. Freepages on isolate pageblock\nshould not be counted for number of freepage.\n\nFollowing is the code snippet in free_pcppages_bulk().\n\n/* MIGRATE_MOVABLE list may include MIGRATE_RESERVEs */\n__free_one_page(page, page_to_pfn(page), zone, 0, mt);\ntrace_mm_page_pcpu_drain(page, 0, mt);\nif (likely(!is_migrate_isolate_page(page))) {\n\t__mod_zone_page_state(zone, NR_FREE_PAGES, 1);\n\tif (is_migrate_cma(mt))\n\t\t__mod_zone_page_state(zone, NR_FREE_CMA_PAGES, 1);\n}\n\nAs you can see above snippet, current code already handle second problem,\nincorrect freepage accounting, by re-fetching pageblock migratetype\nthrough is_migrate_isolate_page(page). But, because this re-fetched\ninformation isn't used for __free_one_page(), first problem would not be\nsolved. This patch try to solve this situation to re-fetch pageblock\nmigratetype before __free_one_page() and to use it for __free_one_page().\n\nIn addition to move up position of this re-fetch, this patch use\noptimization technique, re-fetching migratetype only if there is\nisolate pageblock. Pageblock isolation is rare event, so we can\navoid re-fetching in common case with this optimization.\n\nThis patch also correct migratetype of the tracepoint output.\n\nCc: <stable@vger.kernel.org>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Michal Nazarewicz <mina86@mina86.com>\nAcked-by: Vlastimil Babka <vbabka@suse.cz>\nSigned-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nPatch-mainline: linux-kernel @ 10/31/2014 16:25:28\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/879a0fb672459d62e123c5fc391b57be33c193f9"},{"sha":"e90baccda9e6ff8572897a308310ca9bb59236b1","author":{"email":"bb6c8cfe7699e0f11d1bee88022eb563a5f8e881@lge.com","name":"Joonsoo Kim"},"message":"mm/page_alloc: move freepage counting logic to __free_one_page()\n\nAll the caller of __free_one_page() has similar freepage counting logic,\nso we can move it to __free_one_page(). This reduce line of code and help\nfuture maintenance. This is also preparation step for \"mm/page_alloc:\nrestrict max order of merging on isolated pageblock\" which fix the\nfreepage counting problem on freepage with more than pageblock order.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nPatch-mainline: linux-kernel @ 10/31/2014 16:25:29\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/e90baccda9e6ff8572897a308310ca9bb59236b1"},{"sha":"1093388b715e30c8fafbeb1ff36ad2b7ea9f1354","author":{"email":"bb6c8cfe7699e0f11d1bee88022eb563a5f8e881@lge.com","name":"Joonsoo Kim"},"message":"mm/page_alloc: restrict max order of merging on isolated pageblock Current pageblock isolation logic could isolate each pageblock individually. This causes freepage accounting problem if freepage with pageblock order on isolate pageblock is merged with other freepage on normal pageblock. We can prevent merging by restricting max order of merging to pageblock order if freepage is on isolate pageblock.\n\nA side-effect of this change is that there could be non-merged buddy\nfreepage even if finishing pageblock isolation, because undoing\npageblock isolation is just to move freepage from isolate buddy list to\nnormal buddy list rather than to consider merging.  So, the patch also\nmakes undoing pageblock isolation consider freepage merge.  When\nun-isolation, freepage with more than pageblock order and it's buddy are\nchecked.  If they are on normal pageblock, instead of just moving, we\nisolate the freepage and free it in order to get merged.\n\nSigned-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nAcked-by: Vlastimil Babka <vbabka@suse.cz>\nCc: \"Kirill A. Shutemov\" <kirill@shutemov.name>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>\nCc: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>\nCc: Tang Chen <tangchen@cn.fujitsu.com>\nCc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>\nCc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>\nCc: Wen Congyang <wency@cn.fujitsu.com>\nCc: Marek Szyprowski <m.szyprowski@samsung.com>\nCc: Michal Nazarewicz <mina86@mina86.com>\nCc: Laura Abbott <lauraa@codeaurora.org>\nCc: Heesub Shin <heesub.shin@samsung.com>\nCc: \"Aneesh Kumar K.V\" <aneesh.kumar@linux.vnet.ibm.com>\nCc: Ritesh Harjani <ritesh.list@gmail.com>\nCc: Gioh Kim <gioh.kim@lge.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[lmark@codeaurora.org: fix merge conflicts]\nSigned-off-by: Liam Mark <lmark@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/1093388b715e30c8fafbeb1ff36ad2b7ea9f1354"},{"sha":"6d3f9d665bf34ba99269e9b7a0c51c3babc8790c","author":{"email":"c745fa7b96fe79db6d669643d5feb03ff0641332@gmail.com","name":"Jiang Liu"},"message":"mm: use a dedicated lock to protect totalram_pages and zone->managed_pages\n\nCurrently lock_memory_hotplug()/unlock_memory_hotplug() are used to\nprotect totalram_pages and zone->managed_pages.  Other than the memory\nhotplug driver, totalram_pages and zone->managed_pages may also be\nmodified at runtime by other drivers, such as Xen balloon,\nvirtio_balloon etc.  For those cases, memory hotplug lock is a little\ntoo heavy, so introduce a dedicated lock to protect totalram_pages and\nzone->managed_pages.\n\nNow we have a simplified locking rules totalram_pages and\nzone->managed_pages as:\n\n1) no locking for read accesses because they are unsigned long.\n2) no locking for write accesses at boot time in single-threaded context.\n3) serialize write accesses at runtime by acquiring the dedicated\n   managed_page_count_lock.\n\nAlso adjust zone->managed_pages when freeing reserved pages into the\nbuddy system, to keep totalram_pages and zone->managed_pages in\nconsistence.\n\n[akpm@linux-foundation.org: don't export adjust_managed_page_count to modules (for now)]\nSigned-off-by: Jiang Liu <jiang.liu@huawei.com>\nCc: Mel Gorman <mel@csn.ul.ie>\nCc: Michel Lespinasse <walken@google.com>\nCc: Rik van Riel <riel@redhat.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: \"H. Peter Anvin\" <hpa@zytor.com>\nCc: \"Michael S. Tsirkin\" <mst@redhat.com>\nCc: <sworddragon2@aol.com>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Chris Metcalf <cmetcalf@tilera.com>\nCc: David Howells <dhowells@redhat.com>\nCc: Geert Uytterhoeven <geert@linux-m68k.org>\nCc: Ingo Molnar <mingo@redhat.com>\nCc: Jeremy Fitzhardinge <jeremy@goop.org>\nCc: Jianguo Wu <wujianguo@huawei.com>\nCc: Joonsoo Kim <js1304@gmail.com>\nCc: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nCc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nCc: Marek Szyprowski <m.szyprowski@samsung.com>\nCc: Rusty Russell <rusty@rustcorp.com.au>\nCc: Tang Chen <tangchen@cn.fujitsu.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Wen Congyang <wency@cn.fujitsu.com>\nCc: Will Deacon <will.deacon@arm.com>\nCc: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>\nCc: Yinghai Lu <yinghai@kernel.org>\nCc: Russell King <rmk@arm.linux.org.uk>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: c3d5f5f0c2bc4eabeaf49f1a21e1aeb965246cd2\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[imaund@codeaurora.org: resolve merge conflcits]\nSigned-off-by: Ian Maund <imaund@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/6d3f9d665bf34ba99269e9b7a0c51c3babc8790c"},{"sha":"d1da68a6bae555947e6ffc8a3e87c905b208d664","author":{"email":"c745fa7b96fe79db6d669643d5feb03ff0641332@gmail.com","name":"Jiang Liu"},"message":"mm: introduce helper function mem_init_print_info() to simplify mem_init()\n\nIntroduce helper function mem_init_print_info() to simplify mem_init()\nacross different architectures, which also unifies the format and\ninformation printed.\n\nFunction mem_init_print_info() calculates memory statistics information\nwithout walking each page, so it should be a little faster on some\narchitectures.\n\nAlso introduce another helper get_num_physpages() to kill the global\nvariable num_physpages.\n\nSigned-off-by: Jiang Liu <jiang.liu@huawei.com>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Michel Lespinasse <walken@google.com>\nCc: Rik van Riel <riel@redhat.com>\nCc: Minchan Kim <minchan@kernel.org>\nCc: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: 7ee3d4e8cd560500192d80ca84d7f15d6dee0807\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Ian Maund <imaund@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/d1da68a6bae555947e6ffc8a3e87c905b208d664"},{"sha":"dfe61d2e177440050aa7f551dce2d03cd7225b18","author":{"email":"eec72676ad9a62f2727dfed6d270d98c0d02adec@linux.intel.com","name":"Kirill A. Shutemov"},"message":"mm: allow pgtable_page_ctor() to fail\n\nChange pgtable_page_ctor() return type from void to bool.  Returns true,\nif initialization is successful and false otherwise.\n\nCurrent implementation never fails, but it will change later.\n\nSigned-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Ian Maund <imaund@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/dfe61d2e177440050aa7f551dce2d03cd7225b18"},{"sha":"fc001ee37067e8185a672e3e2921721e95f171b5","author":{"email":"9d4b7fec34444d4f7b5bcba52a53fb47535914f4@motorola.com","name":"Yi-wei Zhao"},"message":"fs:pstore:ramoops: config mem from dt\n\nconfigure the start & size of ramoops memory using device tree.\n\nthe \"dummy\" device is no harm as long as initial mem_size is zero.\n\nSigned-off-by: Yi-wei Zhao <gbjc64@motorola.com>\nReviewed-by: Jeffrey Carlyle <jeff.carlyle@motorola.com>\n\nConflicts:\n\tfs/pstore/ram.c","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/fc001ee37067e8185a672e3e2921721e95f171b5"},{"sha":"04ffc3c0d3497a4751d357a4b19739612331b12a","author":{"email":"b8c5614daf981c6d654e1c0f61da3dc543e98a18@motorola.com","name":"Dmitry Ornatsky"},"message":"fs: pstore: add annotation support\n\nAdd annotation type prz support to pstore. Publish\nannotate function for kernel modules. On warm power\nup pstore will make annotation information found in\nnew ramprz available in annotation-ramoops file.\n\nSigned-off-by: Dmitry Ornatsky <cdo021c@motorola.com>\nReviewed-by: Russell Knize <rknize@motorola.com>\n\nConflicts:\n\tfs/pstore/inode.c\n\tfs/pstore/ram.c","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/04ffc3c0d3497a4751d357a4b19739612331b12a"},{"sha":"339f547b770ec9f4d5abb18223fd040de3c951fd","author":{"email":"f4461cfe90d9062a7e55a35647585f39eb23144b@motorola.com","name":"Yuanyuan Zhong"},"message":"pstore/ram: allow annotation appending\n\nExisting pstore ram annotation stores messages and exports them\nafter reset. Add function which can be used to append messages\nto the annotation after reset and before they are exported to\nannotation-ramoops file.\n\nSigned-off-by: Yuanyuan Zhong <zyy@motorola.com>\nReviewed-by: Yi-Wei Zhao <gbjc64@motorola.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/339f547b770ec9f4d5abb18223fd040de3c951fd"},{"sha":"7cb6a28ec4200a95fc6ecb82c426b76030d42376","author":{"email":"f4461cfe90d9062a7e55a35647585f39eb23144b@motorola.com","name":"Yuanyuan Zhong"},"message":"pstore/ram: export map/unmap functions\n\nExport persistent_ram_map() and persistent_ram_unmap() as\ngeneral purpose functions for mapping and unmapping reserved\nmemory buffer.\n\nSigned-off-by: Yuanyuan Zhong <zyy@motorola.com>\nReviewed-by: Yi-Wei Zhao <gbjc64@motorola.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/7cb6a28ec4200a95fc6ecb82c426b76030d42376"},{"sha":"098d87526420fd03efd1f9d3a13ebbfd132b8e7d","author":{"email":"dab1ac482cbf0c585f9ac2c32308f0f07e56569c@outlook.com","name":"Tkkg1994"},"message":"pstore: whitespace deleted","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/098d87526420fd03efd1f9d3a13ebbfd132b8e7d"},{"sha":"a8d42eb0ee3949941d7a22016f9595548ad77035","author":{"email":"9d4b7fec34444d4f7b5bcba52a53fb47535914f4@motorola.com","name":"Yi-wei Zhao"},"message":"fs/pstore: handle panic kmsg dump\n\nThere are two changes:\n\n1. read \"record size\" and \"dump oops\" from device tree.\n2. only write for KMSG_DUMP_PANIC. When oops happens (panic_on_oops = 1),\nboth oops_exit() and panic() will dump kmsg. Skip KMSG_DUMP_OOPS\nto avoid dump kmsg twice.\n\nSigned-off-by: Yi-wei Zhao <gbjc64@motorola.com>\nReviewed-by: Hong-Mei Li <a21834@motorola.com>","distinct":true,"url":"https://api.github.com/repos/Tkkg1994/Nova-Kernel/commits/a8d42eb0ee3949941d7a22016f9595548ad77035"}]}