public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/8]  drop lock/unlock super
Date: Sat, 06 Oct 2012 12:36:55 +0200	[thread overview]
Message-ID: <507009C7.6010901@gmail.com> (raw)

Hi all,

I send again the patch series to remove from kernel the old lock/unlock 
super. Please consider this patch series for merge window of 3.7. The 
patches are against Linus tree.

Thanks.

Marco Stornelli (8):
   exofs: drop lock/unlock super
   ext3: drop lock/unlock super
   ext4: drop lock/unlock super
   fat: drop lock/unlock super
   hpfs: drop lock/unlock super
   sysv: drop lock/unlock super
   ufs: drop lock/unlock super
   vfs: drop lock/unlock super

  fs/exofs/super.c     |    4 ----
  fs/ext3/super.c      |    6 ------
  fs/ext4/super.c      |   11 +----------
  fs/fat/dir.c         |    4 ++--
  fs/fat/fat.h         |    5 +++--
  fs/fat/inode.c       |    5 +++--
  fs/fat/namei_msdos.c |   26 +++++++++++++-------------
  fs/fat/namei_vfat.c  |   30 +++++++++++++++---------------
  fs/hpfs/super.c      |    3 ---
  fs/super.c           |   23 -----------------------
  fs/sysv/balloc.c     |   18 +++++++++---------
  fs/sysv/ialloc.c     |   14 +++++++-------
  fs/sysv/inode.c      |    4 ++--
  fs/sysv/super.c      |    1 +
  fs/sysv/sysv.h       |    1 +
  fs/ufs/balloc.c      |   30 +++++++++++++++---------------
  fs/ufs/ialloc.c      |   16 ++++++++--------
  fs/ufs/super.c       |   21 +++++++++++----------
  fs/ufs/ufs.h         |    1 +
  include/linux/fs.h   |    1 -
  20 files changed, 92 insertions(+), 132 deletions(-)

-- 
1.7.3.4
---


                 reply	other threads:[~2012-10-06 10:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=507009C7.6010901@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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