From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gan Qixin <ganqixin@huawei.com>
Cc: lvivier@redhat.com, peter.maydell@linaro.org,
zhang.zhanghailiang@huawei.com, mst@redhat.com,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org, f4bug@amsat.org,
alistair.francis@wdc.com, kuhn.chenqun@huawei.com,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 00/10] Fix line over 80 characters warning
Date: Tue, 20 Oct 2020 12:13:46 +0100 [thread overview]
Message-ID: <20201020111346.GH287149@redhat.com> (raw)
In-Reply-To: <20201019203023.658555-1-ganqixin@huawei.com>
On Tue, Oct 20, 2020 at 04:30:13AM +0800, Gan Qixin wrote:
> Hi all,
> I used scripts/checkpatch.pl to find that many files in the hw directory
> contain lines with more than 80 characters. Therefore, I splited some lines to
> fix this warning.
Do we really need to still fix ourselves to a 80 col limit in the
year 2020 ?
Linux increased their max line length to 100 chars and even set
checkpatch.pl to not complain about that limit unless --strict
is given.
80 chars is fine as a "wish list" target, but IMHO the code often
benefits more from exceeding 80 chars, and not wrapping.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-10-20 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 20:30 [PATCH 00/10] Fix line over 80 characters warning Gan Qixin
2020-10-19 20:30 ` [PATCH 01/10] hw/virtio/:split some lines containing more than 80 characters Gan Qixin
2020-10-19 20:30 ` [PATCH 02/10] hw/core/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 03/10] hw/ide/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 04/10] hw/intc/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 05/10] hw/misc/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 06/10] hw/pci/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 07/10] hw/pci-host/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 08/10] hw/char/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 09/10] hw/input/:split " Gan Qixin
2020-10-19 20:30 ` [PATCH 10/10] hw/riscv/:split " Gan Qixin
2020-10-20 11:13 ` Daniel P. Berrangé [this message]
2020-10-20 12:24 ` [PATCH 00/10] Fix line over 80 characters warning ganqixin
2020-10-20 11:14 ` Peter Maydell
2020-10-20 12:24 ` ganqixin
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=20201020111346.GH287149@redhat.com \
--to=berrange@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=ganqixin@huawei.com \
--cc=kuhn.chenqun@huawei.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@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).