mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Kosina <jikos@kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	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 livepatching tree with the ftrace tree
Date: Wed, 27 Nov 2019 11:48:17 +1100	[thread overview]
Message-ID: <20191127114817.71a3b7e9@canb.auug.org.au> (raw)
In-Reply-To: <20191115160319.2d84224d@canb.auug.org.au>

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

Hi all,

On Fri, 15 Nov 2019 16:03:19 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the livepatching tree got a conflict in:
> 
>   tools/testing/selftests/livepatch/Makefile
> 
> between commit:
> 
>   8c666d2ab576 ("selftests/livepatch: Test interaction with ftrace_enabled")
> 
> from the ftrace tree and commit:
> 
>   ecd25094c5f5 ("livepatch: Selftests of the API for tracking system state changes")
> 
> from the livepatching 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 tools/testing/selftests/livepatch/Makefile
> index 1886d9d94b88,1cf40a9e7185..000000000000
> --- a/tools/testing/selftests/livepatch/Makefile
> +++ b/tools/testing/selftests/livepatch/Makefile
> @@@ -5,6 -5,6 +5,7 @@@ TEST_PROGS := 
>   	test-livepatch.sh \
>   	test-callbacks.sh \
>   	test-shadow-vars.sh \
> - 	test-ftrace.sh
> ++	test-ftrace.sh \
> + 	test-state.sh
>   
>   include ../lib.mk

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

-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2019-11-27  0:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  5:03 Stephen Rothwell
2019-11-27  0:48 ` Stephen Rothwell [this message]

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=20191127114817.71a3b7e9@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®