public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	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 fsinfo tree with the kbuid tree
Date: Mon, 17 Aug 2020 09:05:23 +1000	[thread overview]
Message-ID: <20200817090523.68692855@canb.auug.org.au> (raw)
In-Reply-To: <20200805163246.4df09c31@canb.auug.org.au>

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

Hi all,

On Wed, 5 Aug 2020 16:32:46 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the fsinfo tree got a conflict in:
> 
>   samples/vfs/Makefile
> 
> between commit:
> 
>   2f95ada7fe22 ("kbuild: introduce hostprogs-always-y and userprogs-always-y")
> 
> from the kbuid tree and commits:
> 
>   7e786dee0b78 ("fsinfo: Add fsinfo() syscall to query filesystem information")
>   96f310048fba ("fsinfo: sample: Mount listing program")
> 
> from the fsinfo 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.
> 
> diff --cc samples/vfs/Makefile
> index 6377a678134a,7bcdd7a2829e..000000000000
> --- a/samples/vfs/Makefile
> +++ b/samples/vfs/Makefile
> @@@ -1,4 -1,9 +1,4 @@@
>   # SPDX-License-Identifier: GPL-2.0-only
> - userprogs-always-y += test-fsmount test-statx
>  -userprogs := \
>  -	test-fsinfo \
>  -	test-fsmount \
>  -	test-mntinfo \
>  -	test-statx
>  -always-y := $(userprogs)
> ++userprogs-always-y += test-fsinfo test-fsmount test-mntinfo test-statx
>   
>   userccflags += -I usr/include

This is now a conflict between the fsinfo tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2020-08-16 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05  6:32 linux-next: manual merge of the fsinfo tree with the kbuid tree Stephen Rothwell
2020-08-16 23:05 ` Stephen Rothwell [this message]
2020-08-18  8:19   ` David Howells
2020-08-18 10:48     ` 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=20200817090523.68692855@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    /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