public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the perf-current tree
Date: Tue, 5 Sep 2023 13:40:36 -0300	[thread overview]
Message-ID: <ZPdaBAWxzUpr0cdu@kernel.org> (raw)
In-Reply-To: <20230905074350.6a9c81f2@canb.auug.org.au>

Em Tue, Sep 05, 2023 at 07:43:50AM +1000, Stephen Rothwell escreveu:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   10da1b8ed79f ("perf tests mmap-basic: Adapt for riscv")
>   159a8bb06f7b ("libperf: Implement riscv mmap support")
> 
> These are commits
> 
>   26ba042414a3 ("perf: tests: Adapt mmap-basic.c for riscv")
>   60bd50116484 ("tools: lib: perf: Implement riscv mmap support")
> 
> in Linus' tree.

Yeah, I had cherry picked those perf patches at some point, I'll make a
note when submitting to Linus.

Thanks for the report!

- Arnaldo

  reply	other threads:[~2023-09-05 19:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 21:43 linux-next: duplicate patches in the perf-current tree Stephen Rothwell
2023-09-05 16:40 ` Arnaldo Carvalho de Melo [this message]
2023-09-06  0:53   ` Palmer Dabbelt
  -- strict thread matches above, loose matches on Subject: below --
2024-07-16 21:50 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=ZPdaBAWxzUpr0cdu@kernel.org \
    --to=acme@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=palmer@rivosinc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox