linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Arnd Bergmann" <arnd@arndb.de>,
	"\"Jörn Engel\"" <joern@logfs.org>,
	"Christoph Hellwig" <hch@lst.de>
Subject: linux-next: manual merge of the vfs tree with the logfs tree
Date: Fri, 28 May 2010 11:31:14 +1000	[thread overview]
Message-ID: <20100528113114.55b0fdf5.sfr@canb.auug.org.au> (raw)

Hi Al,

Today's linux-next merge of the vfs tree got a conflict in
fs/logfs/logfs.h between commit ddbb5dd99c40a695d5d75645b5a18bef394acb16
("logfs: kill BKL") from the logfs tree and commit
05b2fc7d1f1046fef1199e1a4d2f63df998ef3aa ("drop unused dentry argument to
->fsync") from the vfs tree.

Just context changes.  I fixed it up (see below) and can carry the fix
for a while.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc fs/logfs/logfs.h
index 6365509,c838c4d..0000000
--- a/fs/logfs/logfs.h
+++ b/fs/logfs/logfs.h
@@@ -504,9 -504,9 +504,9 @@@ extern const struct inode_operations lo
  extern const struct file_operations logfs_reg_fops;
  extern const struct address_space_operations logfs_reg_aops;
  int logfs_readpage(struct file *file, struct page *page);
 -int logfs_ioctl(struct inode *inode, struct file *file, unsigned int cmd,
 -		unsigned long arg);
 +long logfs_ioctl(struct file *file, unsigned int cmd,
 +		 unsigned long arg);
- int logfs_fsync(struct file *file, struct dentry *dentry, int datasync);
+ int logfs_fsync(struct file *file, int datasync);
  
  /* gc.c */
  u32 get_best_cand(struct super_block *sb, struct candidate_list *list, u32 *ec);

                 reply	other threads:[~2010-05-28  1:31 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=20100528113114.55b0fdf5.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=hch@lst.de \
    --cc=joern@logfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).