From: rpeterso@redhat.com (Bob Peterson)
To: linux-arm-kernel@lists.infradead.org
Subject: [Cluster-devel] [PATCH 00/12] drop unneeded newline
Date: Tue, 2 Jan 2018 08:52:38 -0500 (EST) [thread overview]
Message-ID: <1878806802.2632123.1514901158666.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1514386305-7402-1-git-send-email-Julia.Lawall@lip6.fr>
----- Original Message -----
| Drop newline at the end of a message string when the printing function adds
| a newline.
Hi Julia,
NACK.
As much as it's a pain when searching the source code for output strings,
this patch set goes against the accepted Linux coding style document. See:
https://www.kernel.org/doc/html/v4.10/process/coding-style.html#breaking-long-lines-and-strings
Regards,
Bob Peterson
next prev parent reply other threads:[~2018-01-02 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 14:51 [PATCH 00/12] drop unneeded newline Julia Lawall
2017-12-27 14:51 ` [PATCH 07/12] ARM: davinci: " Julia Lawall
2018-01-05 13:56 ` Sekhar Nori
2018-01-02 13:52 ` Bob Peterson [this message]
2018-01-02 13:55 ` [Cluster-devel] [PATCH 00/12] " Julia Lawall
2018-01-02 13:56 ` Bob Peterson
2018-01-02 14:00 ` Julia Lawall
2018-01-02 15:11 ` Bart Van Assche
2018-01-02 15:16 ` Julia Lawall
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=1878806802.2632123.1514901158666.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).