public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ian Rogers <irogers@google.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: linux-next: manual merge of the tip tree with the perf tree
Date: Wed, 28 Jun 2023 11:37:48 +1000	[thread overview]
Message-ID: <20230628113748.071d8d80@canb.auug.org.au> (raw)
In-Reply-To: <20230516103413.21e34bb6@canb.auug.org.au>

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

Hi all,

On Tue, 16 May 2023 10:34:13 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the tip tree got conflicts in:
> 
>   tools/perf/arch/x86/include/arch-tests.h
>   tools/perf/arch/x86/tests/arch-tests.c
> 
> between commit:
> 
>   ae4aa00a1a93 ("perf test: Move x86 hybrid tests to arch/x86")
> 
> from the perf tree and commit:
> 
>   78075d947534 ("perf test: Add selftest to test IBS invocation via core pmu events")
> 
> from the tip 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/perf/arch/x86/include/arch-tests.h
> index 33d39c1d3e64,93d3b8877baa..000000000000
> --- a/tools/perf/arch/x86/include/arch-tests.h
> +++ b/tools/perf/arch/x86/include/arch-tests.h
> @@@ -11,7 -11,7 +11,8 @@@ int test__intel_pt_pkt_decoder(struct t
>   int test__intel_pt_hybrid_compat(struct test_suite *test, int subtest);
>   int test__bp_modify(struct test_suite *test, int subtest);
>   int test__x86_sample_parsing(struct test_suite *test, int subtest);
>  +int test__hybrid(struct test_suite *test, int subtest);
> + int test__amd_ibs_via_core_pmu(struct test_suite *test, int subtest);
>   
>   extern struct test_suite *arch_tests[];
>   
> diff --cc tools/perf/arch/x86/tests/arch-tests.c
> index 147ad0638bbb,b5c85ab8d92e..000000000000
> --- a/tools/perf/arch/x86/tests/arch-tests.c
> +++ b/tools/perf/arch/x86/tests/arch-tests.c
> @@@ -22,15 -22,7 +22,16 @@@ struct test_suite suite__intel_pt = 
>   DEFINE_SUITE("x86 bp modify", bp_modify);
>   #endif
>   DEFINE_SUITE("x86 Sample parsing", x86_sample_parsing);
>  +static struct test_case hybrid_tests[] = {
>  +	TEST_CASE_REASON("x86 hybrid event parsing", hybrid, "not hybrid"),
>  +	{ .name = NULL, }
>  +};
>  +
>  +struct test_suite suite__hybrid = {
>  +	.desc = "x86 hybrid",
>  +	.test_cases = hybrid_tests,
>  +};
> + DEFINE_SUITE("AMD IBS via core pmu", amd_ibs_via_core_pmu);
>   
>   struct test_suite *arch_tests[] = {
>   #ifdef HAVE_DWARF_UNWIND_SUPPORT
> @@@ -44,6 -36,6 +45,7 @@@
>   	&suite__bp_modify,
>   #endif
>   	&suite__x86_sample_parsing,
>  +	&suite__hybrid,
> + 	&suite__amd_ibs_via_core_pmu,
>   	NULL,
>   };

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

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2023-06-28  1:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  0:34 linux-next: manual merge of the tip tree with the perf tree Stephen Rothwell
2023-06-28  1:37 ` Stephen Rothwell [this message]
2023-06-28 18:22   ` Namhyung Kim
  -- strict thread matches above, loose matches on Subject: below --
2025-05-26  4:50 Stephen Rothwell
2025-05-28  0:34 ` Stephen Rothwell
2025-06-03  0:46   ` 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=20230628113748.071d8d80@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=acme@redhat.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@amd.com \
    --cc=tglx@linutronix.de \
    /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