From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Wan Jiabing <wanjiabing@vivo.com>, Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Johannes Berg <johannes.berg@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Nick Desaulniers <ndesaulniers@gooogle.com>,
Corey Minyard <cminyard@mvista.com>,
Thomas Meyer <thomas@m3y3r.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Joe Perches <joe@perches.com>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: remove unneeded semicolon in um_arch.c
Date: Sat, 19 Jun 2021 07:41:59 +0100 [thread overview]
Message-ID: <4320e0ea-1339-e2c1-03c0-271dbcd6e22d@cambridgegreys.com> (raw)
In-Reply-To: <20210619020301.77672-1-wanjiabing@vivo.com>
On 19/06/2021 03:02, Wan Jiabing wrote:
> Fix following coccicheck warning:
> ./arch/um/kernel/um_arch.c:284:34-35: Unneeded semicolon
>
> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
> ---
> arch/um/kernel/um_arch.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/um/kernel/um_arch.c b/arch/um/kernel/um_arch.c
> index f9f1463f0521..a149a5e9a16a 100644
> --- a/arch/um/kernel/um_arch.c
> +++ b/arch/um/kernel/um_arch.c
> @@ -281,7 +281,7 @@ static void parse_host_cpu_flags(char *line)
> int i;
> for (i = 0; i < 32*NCAPINTS; i++) {
> if ((x86_cap_flags[i] != NULL) && strstr(line, x86_cap_flags[i]))
> - set_cpu_cap(&boot_cpu_data, i);;
> + set_cpu_cap(&boot_cpu_data, i);
> }
> }
> static void parse_cache_line(char *line)
>
Thanks.
I do not think the patch which introduces this ([v7,1/3] um: Add support
for host CPU flags and alignment) has been merged yet. I do not see it
in the tree as of this morning.
I can see that it is already marked as done in patchwork so it is on its
way.
Richard, what do you want me to do - reissue a fixed one or we should
accept the fix once the original is merged?
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
next prev parent reply other threads:[~2021-06-19 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 2:02 Wan Jiabing
2021-06-19 6:41 ` Anton Ivanov [this message]
2021-06-19 8:04 ` Richard Weinberger
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=4320e0ea-1339-e2c1-03c0-271dbcd6e22d@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cminyard@mvista.com \
--cc=jdike@addtoit.com \
--cc=joe@perches.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=ndesaulniers@gooogle.com \
--cc=richard@nod.at \
--cc=thomas@m3y3r.de \
--cc=wanjiabing@vivo.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
all inboxes | Powered by JetHome®