From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miklos Szeredi <miklos@szeredi•hu>, Theodore Ts'o <tytso@mit•edu>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: manual merge of the overlayfs tree with the ext4 tree
Date: Thu, 24 Mar 2016 10:51:52 +1100 [thread overview]
Message-ID: <20160324105152.56d66cca@canb.auug.org.au> (raw)
Hi Miklos,
Today's linux-next merge of the overlayfs tree got a conflict in:
include/linux/fs.h
fs/overlayfs/super.c
include/linux/dcache.h
between commit:
a7f7fb45f728 ("vfs: add file_dentry()")
from the ext4 tree and commit:
83c2715a73fc ("fs: add file_dentry()")
from the overlayfs tree.
This looks like 2 incompatible versions of the same patch committed to
2 different trees :-( Guys you can't work like this.
Either the patch set was not ready and Ted should not have applied it,
or the new version should not have been added to the overlayfs tree
(especially now, during the merge window). If it was meant to be applied
to more than one tree, it should have been put in a non-rebaing separate
branch that could be merged by each tree.
I fixed it up (I dropped the overlayfs tree for today) 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
reply other threads:[~2016-03-23 23:51 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=20160324105152.56d66cca@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miklos@szeredi$(echo .)hu \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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