From: Warner Losh <imp@bsdimp.com>
To: shiliyang <shiliyang@huawei.com>
Cc: alex.chen@huawei.com, Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
hunongda@huawei.com
Subject: Re: [PATCH V4 0/4] bsd-user: Fix some code style problems
Date: Sun, 17 Jan 2021 19:37:57 -0700 [thread overview]
Message-ID: <CANCZdfoeNh91tEKQB2-AnCrd8RT3tedy67N5JXDFe7kUSkuySg@mail.gmail.com> (raw)
In-Reply-To: <c75512b3-0665-d686-5ea4-248a9819355d@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
Please submit these via http://github.com/qemu-bsd-user/
On Sun, Jan 17, 2021, 7:17 PM shiliyang <shiliyang@huawei.com> wrote:
> This patch series fixes error style problems found by checkpatch.pl.
>
> V3->V4:
> Fix code style problems with branch bsd-user-rebase-3.1.
>
> V2->V3:
> Make the patch into a series.
>
> V1->V2:
> Add cover letter message.
> Fix some style error in patch file before.
>
> Liyang Shi (4):
> bsd-user: "foo * bar" should be "foo *bar"
> bsd-user: suspect code indent for conditional statements
> bsd-user: do not use C99 // comments
> bsd-user: space required after semicolon
>
> bsd-user/bsdload.c | 4 ++--
> bsd-user/elfload.c | 32 ++++++++++++++++----------------
> bsd-user/mmap.c | 25 +++++++++++++------------
> 3 files changed, 31 insertions(+), 30 deletions(-)
>
> --
> 2.29.1.59.gf9b6481aed
>
[-- Attachment #2: Type: text/html, Size: 1356 bytes --]
prev parent reply other threads:[~2021-01-18 2:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 2:17 [PATCH V4 0/4] bsd-user: Fix some code style problems shiliyang
2021-01-18 2:19 ` [PATCH V4 1/4] bsd-user: "foo * bar" should be "foo *bar" shiliyang
2021-01-18 2:20 ` [PATCH V4 2/4] bsd-user: suspect code indent for conditional statements shiliyang
2021-01-18 2:20 ` [PATCH V4 3/4] bsd-user: do not use C99 // comments shiliyang
2021-01-18 2:37 ` Warner Losh
2021-01-18 2:21 ` [PATCH V4 4/4] bsd-user: space required after semicolon shiliyang
2021-01-18 2:35 ` Warner Losh
2021-01-21 3:10 ` shiliyang
2021-01-18 2:37 ` Warner Losh [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=CANCZdfoeNh91tEKQB2-AnCrd8RT3tedy67N5JXDFe7kUSkuySg@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=alex.chen@huawei.com \
--cc=hunongda@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shiliyang@huawei.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;
as well as URLs for NNTP newsgroup(s).