All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>,
	jslaby@suse.cz, "Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the perf tree with Linus' tree
Date: Mon, 4 Nov 2024 10:11:09 -0800	[thread overview]
Message-ID: <ZykOPecMKbqirUZV@google.com> (raw)
In-Reply-To: <20241101103345.45340b53@canb.auug.org.au>

Hello,

On Fri, Nov 01, 2024 at 10:33:45AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the perf tree got a conflict in:
> 
>   tools/perf/util/syscalltbl.c
> 
> between commit:
> 
>   5d35634ecc2d ("perf trace: Fix non-listed archs in the syscalltbl routines")
> 
> from Linus' tree and commit:
> 
>   8c0d1202bad3 ("perf, riscv: Wire up perf trace support for RISC-V")
> 
> from the perf 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.

Thanks for reporting this.  I expected the conflict when I applied the
RISC-V change and now I've merged the perf-tools branch into the
perf-tools-next with the resolution like yours.  So it won't hit the
mainline tree.

Thanks,
Namhyung

  reply	other threads:[~2024-11-04 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 23:33 linux-next: manual merge of the perf tree with Linus' tree Stephen Rothwell
2024-11-04 18:11 ` Namhyung Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-28 21:53 Stephen Rothwell
2023-11-30  0:11 ` Namhyung Kim
2022-07-07 23:28 Stephen Rothwell
2021-10-26 22:17 Stephen Rothwell
2021-10-26 23:06 ` Arnaldo Carvalho de Melo

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=ZykOPecMKbqirUZV@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@redhat.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=bjorn@rivosinc.com \
    --cc=jirislaby@kernel.org \
    --cc=jslaby@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.