mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] nilfs2 updates
Date: Mon, 27 Jul 2020 23:28:28 +0900	[thread overview]
Message-ID: <1595860111-3920-1-git-send-email-konishi.ryusuke@gmail.com> (raw)

Hi Andrew,

Please queue the following changes for the next merge window:

Eric Biggers (1):
  nilfs2: only call unlock_new_inode() if I_NEW

Joe Perches (2):
  nilfs2: Convert __nilfs_msg to integrate the level and format
  nilfs2: Use a more common logging style

In this series,

>  nilfs2: only call unlock_new_inode() if I_NEW

fixes wrong unlock_new_inode() call and related WARNING which can be
triggered from error paths of nilfs_new_inode().

>  nilfs2: Convert __nilfs_msg to integrate the level and format
>  nilfs2: Use a more common logging style

reduce object size and use more common kernel logging styles.

Thanks,
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     | 32 +++++++++----------
 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, 256 insertions(+), 262 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-07-27 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 14:28 Ryusuke Konishi [this message]
2020-07-27 14:28 ` [PATCH 1/3] nilfs2: only call unlock_new_inode() if I_NEW Ryusuke Konishi
2020-07-27 14:28 ` [PATCH 2/3] nilfs2: Convert __nilfs_msg to integrate the level and format Ryusuke Konishi
2020-07-27 14:28 ` [PATCH 3/3] nilfs2: Use a more common logging style Ryusuke Konishi

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=1595860111-3920-1-git-send-email-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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®