public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
	Bob Peterson <rpeterso@redhat.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Price <anprice@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: linux-next: manual merge of the gfs2 tree with the vfs tree
Date: Fri, 12 Jul 2019 10:56:56 +1000	[thread overview]
Message-ID: <20190712105656.04e8ed23@canb.auug.org.au> (raw)
In-Reply-To: <20190708134842.1e947318@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 966 bytes --]

Hi all,

On Mon, 8 Jul 2019 13:48:42 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the gfs2 tree got a conflict in:
> 
>   fs/gfs2/super.c
> 
> between commit:
> 
>   000c8e591016 ("gfs2: Convert gfs2 to fs_context")
> 
> from the vfs tree and commit:
> 
>   5b3a9f348bc5 ("gfs2: kthread and remount improvements")
> 
> from the gfs2 tree.
> 
> I fixed it up (I just used the vfs tree version since it removed some of
> the code modified by the latter) 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.

This is now a conflict between the vfs tree and Linus' tree.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-07-12  0:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  3:48 linux-next: manual merge of the gfs2 tree with the vfs tree Stephen Rothwell
2019-07-12  0:56 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-11  1:12 Stephen Rothwell
2021-06-11  1:46 ` Al Viro
2021-06-11 14:45   ` Andreas Gruenbacher
2021-06-22  1:38 ` Stephen Rothwell
2021-06-22  6:48   ` Andreas Gruenbacher
2021-06-22 21:56     ` Stephen Rothwell
2021-06-09  2:13 Stephen Rothwell
2010-01-27  0:17 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=20190712105656.04e8ed23@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agruenba@redhat.com \
    --cc=anprice@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rpeterso@redhat.com \
    --cc=swhiteho@redhat.com \
    --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