From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Joe Perches <joe@perches.com>,
JFS Discussion <jfs-discussion@lists.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] jfs: logging neatening
Date: Wed, 30 Mar 2016 10:56:55 -0500 [thread overview]
Message-ID: <56FBF747.60306@oracle.com> (raw)
In-Reply-To: <cover.1459340028.git.joe@perches.com>
On 03/30/2016 07:23 AM, Joe Perches wrote:
> This patchset fixes the uses of jfs_info, jfs_warn and jfs_err that
> have terminating newlines and a couple other trivialities to make
> the logging a bit more consistent.
These patches look good. I'm pushing them out to the -next build.
> There is a difference in use between jfs_error and the other
> jfs_info, jfs_warn, and jfs_err logging macros. jfs_error is more
> like the rest of the kernel and requires a newline as the last
> character of the format.
>
> The jfs_info, jfs_warn, and jfs_err macros add the terminating
> newline to the format so the uses do not require them.
I think there's an argument for both ways of doing it. I'm sure I had my
reasons for automatically adding the newline back when I implemented
those macros. (They probably should be inline functions, but that's
another issue.)
> It is a habituated style for many people to add the terminating
> newline for many people and this difference in use between the
> various macro styles causes trivial defects in logging output.
>
> It might be better if the jfs_info, jfs_warn, and jfs_err macros
> were changed to require a newline termination and the uses changed
> to include the newline, but that's a larger change.
Yeah, these patches are the obvious improvement, without changing
anything from a design standpoint.
>
> Joe Perches (3):
> jfs: Remove terminating newlines from jfs_info, jfs_warn, jfs_err uses
> jfs: Remove unnecessary line continuations and terminating newlines
> jfs: Coalesce some formats
>
> fs/jfs/inode.c | 4 ++--
> fs/jfs/jfs_discard.c | 6 ++----
> fs/jfs/jfs_dtree.c | 10 ++++------
> fs/jfs/jfs_imap.c | 3 +--
> fs/jfs/jfs_inode.c | 2 +-
> fs/jfs/jfs_logmgr.c | 14 ++++++--------
> fs/jfs/jfs_txnmgr.c | 21 +++++++++------------
> fs/jfs/namei.c | 4 ++--
> fs/jfs/super.c | 4 ++--
> 9 files changed, 29 insertions(+), 39 deletions(-)
>
next prev parent reply other threads:[~2016-03-30 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 12:23 [PATCH 0/3] jfs: logging neatening Joe Perches
2016-03-30 12:23 ` [PATCH 1/3] jfs: Remove terminating newlines from jfs_info, jfs_warn, jfs_err uses Joe Perches
2016-03-30 12:23 ` [PATCH 2/3] jfs: Remove unnecessary line continuations and terminating newlines Joe Perches
2016-03-30 12:23 ` [PATCH 3/3] jfs: Coalesce some formats Joe Perches
2016-03-30 15:56 ` Dave Kleikamp [this message]
2016-03-30 16:22 ` [PATCH 0/3] jfs: logging neatening Joe Perches
2016-03-30 16:26 ` Dave Kleikamp
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=56FBF747.60306@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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