From: gregkh@linuxfoundation.org (Greg KH)
Subject: [PATCH] staging: erofs: fix parenthesis alignment
Date: Tue, 19 Mar 2019 14:28:49 +0100 [thread overview]
Message-ID: <20190319132849.GA29325@kroah.com> (raw)
In-Reply-To: <20190318235841.21191-1-julianmr97@gmail.com>
On Mon, Mar 18, 2019@08:58:41PM -0300, Julian Merida wrote:
> Fix all checkpatch issues: "CHECK: Alignment should match open parenthesis"
>
> Signed-off-by: Julian Merida <julianmr97 at gmail.com>
> Reviewed-by: Gao Xiang <gaoxiang25 at huawei.com>
Was this really reviewed by Gao? Offline or on-list? I missed it if it
was on-list :(
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-19 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 23:58 [PATCH] staging: erofs: fix parenthesis alignment Julian Merida
2019-03-19 13:28 ` Greg KH [this message]
2019-03-19 13:35 ` Gao Xiang
2019-03-19 17:19 ` Julian Merida
2019-03-20 3:22 ` Gao Xiang
2019-03-20 3:23 ` Gao Xiang
-- strict thread matches above, loose matches on Subject: below --
2019-03-18 4:14 Julian Merida
2019-03-18 7:49 ` Gao Xiang
2019-03-18 23:40 ` Julian Merida
2019-03-12 4:18 Julian Merida
2019-03-12 5:33 ` Gao Xiang
2019-03-12 5:35 ` Gao Xiang
2019-03-18 2:10 ` Julian Merida
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=20190319132849.GA29325@kroah.com \
--to=gregkh@linuxfoundation.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