From: Amit Shah <amit.shah@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: mdroth@linux.vnet.ibm.com, Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-serial: Fix segfault on guest boot
Date: Wed, 22 Jun 2011 10:23:30 +0530 [thread overview]
Message-ID: <20110622045330.GB5789@amit-x200.redhat.com> (raw)
In-Reply-To: <BANLkTinkCkpyP0JDWu5bhAT=XgFbo=ritQ@mail.gmail.com>
On (Sun) 19 Jun 2011 [00:43:20], Blue Swirl wrote:
> On Sat, Jun 18, 2011 at 6:42 AM, Amit Shah <amit.shah@redhat.com> wrote:
> > On (Fri) 17 Jun 2011 [15:08:11], Luiz Capitulino wrote:
> >
> >> > > if (!cpkt.value) {
> >> > > - error_report("virtio-serial-bus: Guest failure in adding device %s\n",
> >> > > - vser->bus.qbus.name);
> >> > > - break;
> >> > > + error_report("virtio-serial-bus: Guest failure in adding device %s\n", vser->bus.qbus.name);
> >> > > + return;
> >> >
> >> > The line split should remain -- else it goes beyond 80 chars.
> >>
> >> It's already beyond 80 chars to me.
> >
> > I prefer to not break strings that get printed out -- makes it easier
> > for greppers to find out the source of the string.
>
> Please read CODING_STYLE and use scripts/checkpatch.pl before
> submitting patches.
Good sense should dictate what goes in CODING_STYLE, not the other way
around.
>From dec93d9eccd639f7bfd1343dca65fa112eb19e3e Mon Sep 17 00:00:00 2001
Message-Id: <dec93d9eccd639f7bfd1343dca65fa112eb19e3e.1308718380.git.amit.shah@redhat.com>
From: Amit Shah <amit.shah@redhat.com>
Date: Wed, 22 Jun 2011 10:20:48 +0530
Subject: [PATCH 1/1] CODING_STYLE: Add exception for log output 80-char limit
Output that's logged can be beyond 80 chars to preserve sane grepping.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
---
CODING_STYLE | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/CODING_STYLE b/CODING_STYLE
index 5ecfa22..886221c 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -31,7 +31,10 @@ Do not leave whitespace dangling off the ends of lines.
2. Line width
-Lines are 80 characters; not longer.
+Lines are 80 characters; not longer. An exception is for output that
+is logged, for example via fprintf() / error_report() functions,
+making it straightforward for people to grep the code for the source
+of the output.
Rationale:
- Some people like to tile their 24" screens with a 6x4 matrix of 80x24
--
1.7.5.4
Amit
next prev parent reply other threads:[~2011-06-22 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 16:38 [Qemu-devel] [PATCH] virtio-serial: Fix segfault on guest boot Luiz Capitulino
2011-06-17 6:47 ` Amit Shah
2011-06-17 7:47 ` Markus Armbruster
2011-06-17 8:44 ` Amit Shah
2011-06-17 13:16 ` Luiz Capitulino
2011-06-17 13:21 ` Luiz Capitulino
2011-06-17 16:09 ` Amit Shah
2011-06-17 18:08 ` Luiz Capitulino
2011-06-18 3:42 ` Amit Shah
2011-06-18 21:43 ` Blue Swirl
2011-06-22 4:53 ` Amit Shah [this message]
2011-06-26 17:43 ` Blue Swirl
2011-06-27 9:48 ` [Qemu-devel] 80-column rule and breaking output statements Amit Shah
2011-07-01 19:43 ` Blue Swirl
2011-07-02 8:38 ` Stefan Hajnoczi
2011-07-04 6:05 ` Amit Shah
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=20110622045330.GB5789@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).