linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git pile 2
Date: Sat, 4 May 2013 21:23:40 +0100	[thread overview]
Message-ID: <20130504202340.GI25399@ZenIV.linux.org.uk> (raw)

Assorted fixes, etc.  Please, pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus

Shortlog:
Al Viro (6):
      do_mount(): fix a leak introduced in 3.9 ("mount: consolidate permission checks")
      do_coredump(): don't wait for thaw if coredump has already been interrupted
      more mode_t whack-a-mole...
      kill fs/read_write.h
      create_mnt_ns: unidiomatic use of list_add()
      xtensa simdisk: fix braino in "xtensa simdisk: switch to proc_create_data()"

Geert Uytterhoeven (2):
      nubus: Kill nubus_proc_detach_device()
      sun3_scsi: add ->show_info()

Han Shen (1):
      Removed unused typedef to avoid "unused local typedef" warnings.

James Hogan (3):
      hostfs: remove "will unlock" comment
      hostfs: move HOSTFS_SUPER_MAGIC to <linux/magic.h>
      hostfs: use kmalloc instead of kzalloc

Jan Kara (1):
      fs: Fix hang with BSD accounting on frozen filesystem

Syam Sidhardhan (1):
      proc_devtree: Replace include linux/module.h with linux/export.h

Wei Yongjun (1):
      vfs: use list_move instead of list_del/list_add

Yan, Zheng (1):
      fs: remove dentry_lru_prune()

Diffstat:
 arch/xtensa/platforms/iss/simdisk.c |    2 +-
 drivers/hwmon/abx500.c              |    2 +-
 drivers/nubus/proc.c                |   15 ---
 drivers/scsi/sun3_NCR5380.c         |  185 +++++++++++++++--------------------
 drivers/scsi/sun3_scsi.c            |    1 +
 drivers/scsi/sun3_scsi.h            |    2 +-
 fs/compat.c                         |    2 -
 fs/compat_ioctl.c                   |    1 -
 fs/coredump.c                       |    9 +-
 fs/dcache.c                         |   34 ++-----
 fs/hostfs/hostfs_kern.c             |    8 +-
 fs/namespace.c                      |    7 +-
 fs/proc/proc_devtree.c              |    2 +-
 fs/read_write.c                     |    5 +-
 fs/read_write.h                     |    9 --
 include/linux/fs.h                  |    7 ++
 include/linux/nubus.h               |    1 -
 include/uapi/linux/magic.h          |    1 +
 kernel/acct.c                       |    7 +-
 19 files changed, 124 insertions(+), 176 deletions(-)
 delete mode 100644 fs/read_write.h

             reply	other threads:[~2013-05-04 20:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04 20:23 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-02 12:38 [git pull] vfs.git, pile 2 Al Viro
2016-12-16 22:12 [git pull] vfs.git " Al Viro
2016-12-18  2:49 ` Linus Torvalds
2016-12-18  3:26   ` Al Viro
2016-12-18  3:34     ` Linus Torvalds
2016-12-18  4:06       ` Al Viro
2016-12-18 23:40         ` Darrick J. Wong
2014-12-15 23:51 Al Viro
2014-12-16 13:33 ` Al Viro
2014-12-16 18:06   ` Al Viro
2012-10-12  1:19 [git pull] vfs.git, " Al Viro

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=20130504202340.GI25399@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).