From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] nilfs2: Logging style changes
Date: Fri, 03 Apr 2020 22:31:47 +0900 (JST) [thread overview]
Message-ID: <20200403.223147.300007237674208339.konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <cover.1584894497.git.joe@perches.com>
On Sun, 22 Mar 2020 09:38:09 -0700, Joe Perches <joe@perches.com> wrote:
> Reduce object size and use more common kernel logging styles.
>
> Joe Perches (2):
> nilfs2: Convert __nilfs_msg to integrate the level and format
> nilfs2: Use a more common logging style
Applied. Thank you.
Ryusuke Konishi
>
> fs/nilfs2/alloc.c | 38 +++++++++----------
> fs/nilfs2/btree.c | 42 ++++++++++-----------
> fs/nilfs2/cpfile.c | 10 ++---
> fs/nilfs2/dat.c | 14 +++----
> fs/nilfs2/direct.c | 14 ++++---
> fs/nilfs2/gcinode.c | 2 +-
> fs/nilfs2/ifile.c | 4 +-
> fs/nilfs2/inode.c | 29 +++++++--------
> fs/nilfs2/ioctl.c | 37 +++++++++----------
> fs/nilfs2/mdt.c | 2 +-
> fs/nilfs2/namei.c | 6 +--
> fs/nilfs2/nilfs.h | 18 ++++++---
> fs/nilfs2/page.c | 11 +++---
> fs/nilfs2/recovery.c | 32 +++++++---------
> fs/nilfs2/segbuf.c | 2 +-
> fs/nilfs2/segment.c | 38 +++++++++----------
> fs/nilfs2/sufile.c | 29 +++++++--------
> fs/nilfs2/super.c | 73 +++++++++++++++++++------------------
> fs/nilfs2/sysfs.c | 29 +++++++--------
> fs/nilfs2/the_nilfs.c | 85 ++++++++++++++++++++-----------------------
> 20 files changed, 254 insertions(+), 261 deletions(-)
>
> --
> 2.24.0
>
prev parent reply other threads:[~2020-04-03 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 16:38 Joe Perches
2020-03-22 16:38 ` [PATCH 1/2] nilfs2: Convert __nilfs_msg to integrate the level and format Joe Perches
2020-03-22 16:38 ` [PATCH 2/2] nilfs2: Use a more common logging style Joe Perches
2020-04-03 13:31 ` Ryusuke Konishi [this message]
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=20200403.223147.300007237674208339.konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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
all inboxes | Powered by JetHome®