linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: sfr@canb.auug.org.au
Cc: viro@ZenIV.linux.org.uk, linux-next@vger.kernel.org, hch@lst.de,
	tj@kernel.org, miklos@szeredi.hu
Subject: Re: linux-next: manual merge of the vfs tree with the  tree
Date: Fri, 08 May 2009 15:40:49 +0200	[thread overview]
Message-ID: <E1M2QJl-00035r-E2@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20090508144457.c88fc3dc.sfr@canb.auug.org.au> (message from Stephen Rothwell on Fri, 8 May 2009 14:44:57 +1000)

On Fri, 8 May 2009, Stephen Rothwell wrote:
> Today's linux-next merge of the vfs tree got a conflict in
> fs/fuse/inode.c between commit a325f9b92273d6c64ec56167905b951b9827ec33
> ("fuse: update fuse_conn_init() and separate out fuse_conn_kill()") from
> the fuse tree and commit 4225d95ddb751e09da0c145b58549da95ba13e3a ("push
> BKL down into ->put_super") from the vfs tree.
> 
> I fixed it up (see below - please check) and can carry the fix as
> necessary.

The fixup looks good.

Al, would it make sense to merge the fuse tree into the vfs tree at
some point to fix the conflict permanently?

If so, please pull from

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git cuse

to receive the following changes.

Thanks,
Miklos
----

Miklos Szeredi (11):
      fuse: destroy bdi on error
      fuse: use struct path in release structure
      fuse: clean up fuse_write_fill()
      fuse: prepare fuse_direct_io() for CUSE
      fuse: add members to struct fuse_file
      fuse: don't use inode in helpers called by fuse_direct_io()
      fuse: clean up args in fuse_finish_open() and fuse_release_fill()
      fuse: create fuse_do_open() helper for CUSE
      fuse: don't use inode in fuse_sync_release()
      fuse: don't use inode in fuse_do_ioctl() helper
      fuse: don't use inode in fuse_file_poll

Tejun Heo (4):
      fuse: misc cleanups
      fuse: update fuse_conn_init() and separate out fuse_conn_kill()
      fuse: export symbols to be used by CUSE
      CUSE: implement CUSE - Character device in Userspace

---
 fs/Kconfig            |   10 +
 fs/fuse/Makefile      |    1 +
 fs/fuse/cuse.c        |  610 +++++++++++++++++++++++++++++++++++++++++++++++++
 fs/fuse/dev.c         |   15 +-
 fs/fuse/dir.c         |   33 +--
 fs/fuse/file.c        |  346 ++++++++++++++++------------
 fs/fuse/fuse_i.h      |   47 +++-
 fs/fuse/inode.c       |  117 ++++++----
 include/linux/fuse.h  |   31 +++
 include/linux/magic.h |    5 +-
 10 files changed, 983 insertions(+), 232 deletions(-)
 create mode 100644 fs/fuse/cuse.c

  reply	other threads:[~2009-05-08 13:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  4:44 linux-next: manual merge of the vfs tree with the tree Stephen Rothwell
2009-05-08 13:40 ` Miklos Szeredi [this message]
2009-05-08 17:50   ` Al Viro
2009-05-09 16:58     ` Miklos Szeredi
2009-05-13  2:20 Stephen Rothwell
2009-05-22  1:23 Stephen Rothwell
2009-05-24 22:03 ` Frederic Weisbecker
2009-05-24 22:07   ` Christoph Hellwig
2009-05-25 17:10     ` Frederic Weisbecker
2009-05-25  6:50   ` Stephen Rothwell
2009-06-09  1:08 Stephen Rothwell
2009-06-09  6:58 ` Miklos Szeredi
2009-06-09  7:27   ` Stephen Rothwell
2012-09-24  1:45 Stephen Rothwell
2014-05-29  3:25 Stephen Rothwell
2015-06-05  5:46 mpe@ellerman.id.au

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=E1M2QJl-00035r-E2@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=hch@lst.de \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).