From: Joe Perches <joe@perches.com>
To: "Krzysztof Hałasa" <khalasa@piap.pl>,
"Mario Bambagini" <mario.bambagini@gmail.com>
Cc: linux-kernel@vger.kernel.org, driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH] defines modified to match the 80-char rule
Date: Wed, 01 Jul 2015 23:20:26 -0700 [thread overview]
Message-ID: <1435818026.2487.5.camel@perches.com> (raw)
In-Reply-To: <m38ub0qpei.fsf@t19.piap.pl>
On Wed, 2015-07-01 at 09:59 +0200, Krzysztof Hałasa wrote:
> Mario Bambagini <mario.bambagini@gmail.com> writes:
>
> > Defines have been written in more than one line to match the 80-character
> > rule. This error has been fixed 6 times in this file.
> > The file is fully compliant with respect to the coding rules now.
>
> Rules, maybe. But is it better, i.e., more readable?
>
> > --- a/drivers/staging/lustre/include/linux/libcfs/libcfs_debug.h
> > +++ b/drivers/staging/lustre/include/linux/libcfs/libcfs_debug.h
[]
> > -#define LCONSOLE(mask, format, ...) CDEBUG(D_CONSOLE | (mask), format, ## __VA_ARGS__)
[]
> > +#define LCONSOLE(mask, format, ...) \
> > + CDEBUG(D_CONSOLE | (mask), format, ## __VA_ARGS__)
> ... I don't think so. Perhaps if I wasn't using the bleading edge tech
> 132-column digital flat LCD screen, I would see this differently (Emacs
> isn't perfect when displaying long lines on IBM monochrome display
> adapter, even with the intelligent-long-lines-wrap package).
I think this isn't particularly nice because of the
different alignment styles used for the macros.
I think it's OK as is, but it _might_ be nicer if it
removed the space after ## and used the same indent
as most other macros.
#define LCONSOLE(mask, fmt, ...) \
CDEBUG(D_CONSOLE | (mask), fmt, ##__VA_ARGS__)
and
#define LCONSOLE_ERROR_MSG(errnum, fmt, ...) \
CDEBUG_LIMIT(D_CONSOLE | D_ERROR, "%x-%x: " fmt, \
errnum, LERRCHKSUM(errnum), ##__VA_ARGS__)
next prev parent reply other threads:[~2015-07-02 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 21:21 [PATCH] defines modified to match the 80-char rule Mario Bambagini
2015-07-01 7:59 ` Krzysztof Hałasa
2015-07-02 6:20 ` Joe Perches [this message]
2015-07-02 18:01 ` Joe Perches
2015-07-03 10:58 ` Krzysztof Hałasa
2015-07-03 16:10 ` Joe Perches
2015-07-06 6:07 ` Krzysztof Hałasa
2015-07-06 8:07 ` Joe Perches
2015-07-06 12:16 ` Krzysztof Hałasa
2015-07-08 15:30 ` Joe Perches
2015-07-06 8:30 ` Dan Carpenter
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=1435818026.2487.5.camel@perches.com \
--to=joe@perches.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=khalasa@piap.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.bambagini@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.