At the end of get_last_crashkernel(), the judgement of ck_cmdline is
obviously unnecessary and causes redundance, let's clean it up.
Signed-off-by: lizhe
Acked-by: Baoquan He
Acked-by: Philipp Rudo
---
kernel/crash_core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/k
At the end of get_last_crashkernel(), the judgement of ck_cmdline is
obviously unnecessary and causes redundance, let's clean it up.
Signed-off-by: lizhe
Acked-by: Baoquan He
Acked-by: Philipp Rudo
---
kernel/crash_core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/k
When ck_cmdline is NULL. The last three lines of
this function(get_last_crashkernel()) are equivalent to :
if (!NULL)
return NULL;
return NULL;
This is obviously a redundant check
Signed-off-by: lizhe
---
kernel/crash_core.c | 3 ---
1 file changed, 3 deletions
When ck_cmdline is NULL, the only caller of get_last_crashkernel()
has already done non-NULL check(see __parse_crashkernel()),
so it doesn't make any sense to make a check here
Signed-off-by: lizhe
---
kernel/crash_core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/k
No judgment required ck_cmdline is NULL
its caller has alreadly judged, see __parse_crashkernel
function
Signed-off-by: lizhe
---
kernel/crash_core.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index eb53f5ec62c9..9981cf9b9fe4 100644
--- a
