From: Baoquan He <bhe@redhat.com>
To: Philipp Rudo <prudo@redhat.com>
Cc: lizhe <sensor1010@163.com>,
dyoung@redhat.com, vgoyal@redhat.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/crash_core.c: No judgment required
Date: Mon, 25 Apr 2022 09:36:17 +0800 [thread overview]
Message-ID: <YmX7EW4Gs+c1ZueQ@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20211214173242.192f47e8@rhtmp>
On 12/14/21 at 05:32pm, Philipp Rudo wrote:
> Hi lizhe,
>
> On Thu, 9 Dec 2021 19:20:03 -0800
> lizhe <sensor1010@163.com> wrote:
>
> > No judgment required ck_cmdline is NULL
> > its caller has alreadly judged, see __parse_crashkernel
> > function
> >
> > Signed-off-by: lizhe <sensor1010@163.com>
> > ---
> > 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/kernel/crash_core.c
> > +++ b/kernel/crash_core.c
> > @@ -221,9 +221,6 @@ static __init char *get_last_crashkernel(char *cmdline,
> > p = strstr(p+1, name);
> > }
> >
> > - if (!ck_cmdline)
> > - return NULL;
> > -
> > return ck_cmdline;
> > }
> >
>
> I agree that the if-block is not needed and can be removed. However, I
> cannot follow your reasoning in the commit message. Could you please
> explain it in more detail.
>
> The reason why I think that the 'if' can be removed is that the
> expression can only be true when ck_cmdline = NULL. But with that the
> last three lines are equivalent to
>
> if (!ck_cmdline)
> return ck_cmdline;
>
> return ck_cmdline;
>
> Which simply doesn't make any sense.
Right, the judgement actually introduces redundant codes. As Zhe
replied, maybe you can rewrite the log and repost with your
Signed-off-by, Philipp. As for Author, you two can discuss in private
mail.
next prev parent reply other threads:[~2022-04-25 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 3:20 [PATCH] kernel/crash_core.c: No judgment required lizhe
2021-12-14 16:32 ` Philipp Rudo
2022-04-25 1:36 ` Baoquan He [this message]
[not found] ` <62058381.3b6e.1805f62c8f4.Coremail.sensor1010@163.com>
2022-04-26 8:17 ` Philipp Rudo
2022-04-26 8:20 ` Philipp Rudo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YmX7EW4Gs+c1ZueQ@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=sensor1010@163.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox