From: Thomas Gleixner <tglx@linutronix.de>
To: Chao Fan <fanc.fnst@cn.fujitsu.com>
Cc: hpa@zytor.com, mingo@redhat.com, x86@kernel.org,
keescook@chromium.org, gregkh@linuxfoundation.org,
n-horiguchi@ah.jp.nec.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kaslr: clean up a useless variable and some usless space
Date: Thu, 23 Nov 2017 17:35:06 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1711231734390.1724@nanos> (raw)
In-Reply-To: <alpine.DEB.2.20.1711231732560.1724@nanos>
On Thu, 23 Nov 2017, Thomas Gleixner wrote:
> On Thu, 23 Nov 2017, Chao Fan wrote:
>
> > There are two same variable "rc" in mem_avoid_memmap. One is in the
> > circulation, the other is out of the circulation. The one out will never
> > be used, so drop it.
> >
> > Signed-off-by: Chao Fan <fanc.fnst@cn.fujitsu.com>
> > ---
> > arch/x86/boot/compressed/kaslr.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kaslr.c
> > index a63fbc25ce84..8199a6187251 100644
> > --- a/arch/x86/boot/compressed/kaslr.c
> > +++ b/arch/x86/boot/compressed/kaslr.c
> > @@ -171,7 +171,6 @@ parse_memmap(char *p, unsigned long long *start, unsigned long long *size)
> > static void mem_avoid_memmap(char *str)
> > {
> > static int i;
> > - int rc;
> >
> > if (i >= MAX_MEMMAP_REGIONS)
> > return;
> > @@ -219,7 +218,7 @@ static int handle_mem_memmap(void)
> > return 0;
> >
> > tmp_cmdline = malloc(len + 1);
> > - if (!tmp_cmdline )
> > + if (!tmp_cmdline)
> > error("Failed to allocate space for tmp_cmdline");
>
> This change is unrelated.
Never mind. Just noticed that it's mentioned in $subject.
next prev parent reply other threads:[~2017-11-23 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 9:08 Chao Fan
2017-11-23 16:34 ` Thomas Gleixner
2017-11-23 16:35 ` Thomas Gleixner [this message]
2017-11-23 19:24 ` [tip:x86/urgent] x86/boot/KASLR: Remove unused variable tip-bot for Chao Fan
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=alpine.DEB.2.20.1711231734390.1724@nanos \
--to=tglx@linutronix.de \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®