linux-next.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>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	DongOh Shin <doscode.kr@gmail.com>
Subject: linux-next: manual merge of the vfs tree with the f2fs tree
Date: Mon, 27 Feb 2017 11:05:53 +1100	[thread overview]
Message-ID: <20170227110553.0bb24b02@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the vfs tree got a conflict in:

  fs/f2fs/f2fs.h

between commit:

  cac5a3d8f517 ("f2fs: fix 446 coding style warnings in f2fs.h")

from the f2fs tree and commit:

  caffc373c573 ("statx: Add a system call to make enhanced file info available")

from the vfs tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc fs/f2fs/f2fs.h
index d1483136fed6,db1f5f6a0d04..000000000000
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@@ -2036,17 -1962,16 +2036,17 @@@ static inline void *f2fs_kvzalloc(size_
  /*
   * file.c
   */
 -int f2fs_sync_file(struct file *, loff_t, loff_t, int);
 -void truncate_data_blocks(struct dnode_of_data *);
 -int truncate_blocks(struct inode *, u64, bool);
 -int f2fs_truncate(struct inode *);
 -int f2fs_getattr(const struct path *, struct kstat *, u32, unsigned int);
 -int f2fs_setattr(struct dentry *, struct iattr *);
 -int truncate_hole(struct inode *, pgoff_t, pgoff_t);
 -int truncate_data_blocks_range(struct dnode_of_data *, int);
 -long f2fs_ioctl(struct file *, unsigned int, unsigned long);
 -long f2fs_compat_ioctl(struct file *, unsigned int, unsigned long);
 +int f2fs_sync_file(struct file *file, loff_t start, loff_t end, int datasync);
 +void truncate_data_blocks(struct dnode_of_data *dn);
 +int truncate_blocks(struct inode *inode, u64 from, bool lock);
 +int f2fs_truncate(struct inode *inode);
- int f2fs_getattr(struct vfsmount *mnt, struct dentry *dentry,
- 			struct kstat *stat);
++int f2fs_getattr(const struct path *path, struct kstat *stat, u32 request_mask,
++		 unsigned int query_flags);
 +int f2fs_setattr(struct dentry *dentry, struct iattr *attr);
 +int truncate_hole(struct inode *inode, pgoff_t pg_start, pgoff_t pg_end);
 +int truncate_data_blocks_range(struct dnode_of_data *dn, int count);
 +long f2fs_ioctl(struct file *filp, unsigned int cmd, unsigned long arg);
 +long f2fs_compat_ioctl(struct file *file, unsigned int cmd, unsigned long arg);
  
  /*
   * inode.c

             reply	other threads:[~2017-02-27  0:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  0:05 Stephen Rothwell [this message]
2017-02-27  8:27 ` linux-next: manual merge of the vfs tree with the f2fs tree David Howells
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 23:47 Stephen Rothwell
2023-12-20  0:13 ` Stephen Rothwell
2023-12-20  1:34   ` Al Viro
2023-12-20  3:05     ` Stephen Rothwell
2023-12-20  4:44       ` Al Viro
2021-04-19  0:53 Stephen Rothwell
2018-10-03  0:12 Stephen Rothwell
2017-11-08 23:06 Stephen Rothwell
2017-11-08 23:01 Stephen Rothwell
2016-07-25  0:21 Stephen Rothwell
2016-05-03  1:41 Stephen Rothwell
2015-05-07  2:05 Stephen Rothwell
2015-04-13  1:53 Stephen Rothwell
2014-06-10  1:23 Stephen Rothwell
2014-04-29  0:37 Stephen Rothwell

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=20170227110553.0bb24b02@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=doscode.kr@gmail.com \
    --cc=jaegeuk@kernel.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).