From: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Jakub Kunert
<kuba.kunert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/6] cgroup: Remove prohibited white spaces
Date: Wed, 16 Dec 2015 09:22:05 +0800 [thread overview]
Message-ID: <5670BCBD.9000804@huawei.com> (raw)
In-Reply-To: <1450182045-27480-1-git-send-email-kuba.kunert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Jakub,
On 2015/12/15 20:20, Jakub Kunert wrote:
> This patch fixes the checkpatch.pl error:
>
> ERROR: space prohibited before open square bracket
>
checkpatch.pl should be used to check patches that are going to be
sent to the mailing list, and normally should not be used to check
againt existing code.
prev parent reply other threads:[~2015-12-16 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:20 [PATCH 1/6] cgroup: Remove prohibited white spaces Jakub Kunert
[not found] ` <1450182045-27480-1-git-send-email-kuba.kunert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 12:20 ` [PATCH 2/6] cgroup: Fix line length to 80 characters Jakub Kunert
[not found] ` <1450182045-27480-2-git-send-email-kuba.kunert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 17:11 ` Tejun Heo
2015-12-15 12:20 ` [PATCH 3/6] cgroup: Fix trailing */ in block comments Jakub Kunert
2015-12-15 12:20 ` [PATCH 4/6] cgroup: Add blank lines after declarations Jakub Kunert
2015-12-15 12:20 ` [PATCH 5/6] cgroup: Replace printk(KERN_INFO) with pr_info() Jakub Kunert
2015-12-15 12:20 ` [PATCH 6/6] cgroup: Move constant to the right site of comparison Jakub Kunert
2015-12-15 17:06 ` [PATCH 1/6] cgroup: Remove prohibited white spaces Tejun Heo
2015-12-16 1:22 ` Zefan Li [this message]
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=5670BCBD.9000804@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kuba.kunert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).