From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v5 0/3] Simplify network setup
Date: Thu, 4 May 2017 13:27:47 +0200 [thread overview]
Message-ID: <20170504132747.3d799242@linux-v3j5> (raw)
In-Reply-To: <20170503160751.1634-1-pvorel@suse.cz>
Hi,
On Wed, 3 May 2017 18:07:48 +0200
"Petr Vorel" <pvorel@suse.cz> wrote:
> BTW: I probably have source lines > 80 chars. My Vim doesn't highlight
> anything, but checkpatch.pl complain. I might have wrong vim configuration.
Are you using checkpatch.pl from kernel 4.11? It was recently changed to
follow the actual style guidelines which say lines over 80 chars are
preferable to strings being split over multiple lines. Maybe Vim is aware of
that?
Thank you,
Richard.
next prev parent reply other threads:[~2017-05-04 11:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:07 [LTP] [RFC PATCH v5 0/3] Simplify network setup Petr Vorel
2017-05-03 16:07 ` [LTP] [RFC PATCH v5 1/3] gitignore: Prefixing filenames Petr Vorel
2017-05-03 16:07 ` [LTP] [RFC PATCH v5 2/3] network: Add tool for setup IP variables Petr Vorel
2017-05-04 14:41 ` Richard Palethorpe
2017-05-04 19:51 ` Petr Vorel
2017-05-03 16:07 ` [LTP] [RFC PATCH v5 3/3] network: Use tst_net_vars to set up IPv4 and IPv6 related variables Petr Vorel
2017-05-04 11:09 ` [LTP] [RFC PATCH v5 0/3] Simplify network setup Alexey Kodanev
2017-05-04 12:42 ` Alexey Kodanev
2017-05-04 14:03 ` Petr Vorel
2017-05-04 13:46 ` Petr Vorel
2017-05-04 14:52 ` Alexey Kodanev
2017-05-04 19:25 ` Petr Vorel
2017-05-04 11:27 ` Richard Palethorpe [this message]
2017-05-04 12:35 ` Alexey Kodanev
2017-05-04 13:38 ` Petr Vorel
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=20170504132747.3d799242@linux-v3j5 \
--to=rpalethorpe@suse.com \
--cc=ltp@lists.linux.it \
/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