From: Jeff Layton <jlayton@poochiereds.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the akpm tree with the wberr tree
Date: Tue, 01 Aug 2017 06:59:19 -0400 [thread overview]
Message-ID: <1501585159.4702.0.camel@poochiereds.net> (raw)
In-Reply-To: <20170801154634.0a01acdc@canb.auug.org.au>
On Tue, 2017-08-01 at 15:46 +1000, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> include/linux/fs.h
>
> between commit:
>
> 9dcc0577f2a4 ("mm: remove optimizations based on i_size in mapping writeback waits")
>
> from the wberr tree and patch:
>
> "mm: remove optimizations based on i_size in mapping writeback waits"
>
> from the akpm tree.
>
> I fixed it up (I just dropped the akpm tree patch) 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.
>
I didn't realize that Andrew was going to pick that one up. I'll drop it
from my tree.
Thanks!
--
Jeff Layton <jlayton@poochiereds.net>
next prev parent reply other threads:[~2017-08-01 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 5:46 linux-next: manual merge of the akpm tree with the wberr tree Stephen Rothwell
2017-08-01 10:59 ` Jeff Layton [this message]
2017-08-01 11:31 ` Jeff Layton
2017-08-01 22:32 ` Andrew Morton
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=1501585159.4702.0.camel@poochiereds.net \
--to=jlayton@poochiereds.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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