From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Linux 3.6-rc1
Date: Sat, 4 Aug 2012 07:19:04 +0100 [thread overview]
Message-ID: <20120804061904.GJ23464@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1344058715.1716.1.camel@kyv>
On Sat, Aug 04, 2012 at 08:38:35AM +0300, Artem Bityutskiy wrote:
> On Sat, 2012-08-04 at 05:46 +0100, Al Viro wrote:
> > OK... I've ported Artem's patchset on top of exofs merge; Artem, could
> > you check if you are OK with the result currently in vfs.git#for-linus?
>
> Thanks Al, yes, it looks all right.
OK, then... Artem's patchset + do_dentry_open() fix is in the usual place -
git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Please, pull...
Shortlog:
Al Viro (1):
missed mnt_drop_write() in do_dentry_open()
Artem Bityutskiy (15):
vfs: kill write_super and sync_supers
Documentation: get rid of write_super
Documentation: fix the VM knobs descritpion WRT pdflush
ext3: nuke write_super from comments
ext4: nuke write_super from comments
ext4: nuke pdflush from comments
btrfs: nuke write_super from comments
btrfs: nuke pdflush from comments
jbd/jbd2: nuke write_super from comments
vfs: nuke pdflush from comments
hfs: nuke write_super from comments
nilfs2: nuke write_super from comments
drbd: nuke pdflush from comments
gfs2: nuke pdflush from comments
UBIFS: nuke pdflush from comments
Diffstat:
Documentation/DocBook/filesystems.tmpl | 4 +-
Documentation/filesystems/Locking | 2 -
Documentation/filesystems/porting | 5 +--
Documentation/filesystems/vfs.txt | 4 --
Documentation/laptops/laptop-mode.txt | 12 ++++----
Documentation/sysctl/vm.txt | 14 ++++----
Documentation/sysctl/vm.txt.rej | 21 +++++++++++++
drivers/block/drbd/drbd_main.c | 4 +-
fs/bio.c | 2 +-
fs/btrfs/inode.c | 3 +-
fs/btrfs/ordered-data.c | 2 +-
fs/btrfs/super.c | 4 --
fs/btrfs/volumes.c | 4 --
fs/ext3/inode.c | 8 -----
fs/ext3/super.c | 11 -------
fs/ext4/inode.c | 10 +-----
fs/ext4/super.c | 11 -------
fs/gfs2/meta_io.c | 2 +-
fs/hfs/mdb.c | 4 +-
fs/jbd/journal.c | 4 +-
fs/jbd2/journal.c | 4 +-
fs/nilfs2/super.c | 4 --
fs/nilfs2/the_nilfs.h | 2 -
fs/open.c | 2 +-
fs/super.c | 40 ------------------------
fs/ubifs/file.c | 10 +++---
fs/ubifs/super.c | 2 +-
include/linux/backing-dev.h | 1 -
include/linux/fs.h | 3 --
include/linux/writeback.h | 1 -
mm/backing-dev.c | 52 --------------------------------
mm/page-writeback.c | 1 -
32 files changed, 59 insertions(+), 194 deletions(-)
create mode 100644 Documentation/sysctl/vm.txt.rej
next prev parent reply other threads:[~2012-08-04 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 1:17 Linux 3.6-rc1 Linus Torvalds
2012-08-03 6:47 ` Artem Bityutskiy
2012-08-03 20:23 ` Linus Torvalds
2012-08-04 4:46 ` Al Viro
2012-08-04 5:38 ` Artem Bityutskiy
2012-08-04 6:19 ` Al Viro [this message]
2012-08-04 7:51 ` Dongsheng Song
2012-08-04 8:19 ` Al Viro
2012-08-04 5:43 ` Artem Bityutskiy
2012-08-03 19:01 ` Nicholas A. Bellinger
2012-08-04 0:02 ` [PATCH] pstore: fix printk format warning Randy Dunlap
2012-08-04 1:15 ` Anton Vorontsov
2012-08-04 1:32 ` Randy Dunlap
2012-08-04 1:35 ` Kees Cook
2012-08-06 16:07 ` Luck, Tony
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=20120804061904.GJ23464@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dedekind1@gmail.com \
--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