All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, agordeev@linux.ibm.com,
	gor@linux.ibm.com, sumanthk@linux.ibm.com, hca@linux.ibm.com,
	japo@linux.ibm.com
Subject: Re: [PATCH] perf callchain: Handle multiple address spaces
Date: Tue, 5 May 2026 21:57:30 -0300	[thread overview]
Message-ID: <afqR-mL5g26ar72N@x1> (raw)
In-Reply-To: <afnq38nWs-6wHinY@x1>

On Tue, May 05, 2026 at 10:04:31AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, May 05, 2026 at 07:50:49AM +0200, Thomas Richter wrote:
> > On 5/5/26 01:48, Namhyung Kim wrote:
> > > On Mon, May 04, 2026 at 11:56:15AM +0200, Thomas Richter wrote:
> > >> On 4/30/26 04:57, Namhyung Kim wrote:
> > >>> On Wed, Apr 29, 2026 at 09:14:38AM +0200, Thomas Richter wrote:
 
> > >>>> is there something which needs to be done on my side to get this patch picked?
> > >>>> It still fails on s390.
 
> > >>>> Please adviseon how to proceed.
 
> > >>> Arnaldo will take care of 7.2 development cycle.
 
> > >> Today we are at v7.1-rc2. Does this mean the fix won't make it into v7.1 at all
> > >> and we have to wait roughly 2 month?
 
> > > Just out of curiousity, do you plan to use v7.1 for this feature
> > > specifically or just for test failures?  Probably better to use v7.2
> > > series (i.e. perf-tools-next) instead?
  
> > Right now I just care for failing test features. I am fine with 7.2
> > as long as it gets picked.
 
> I'll pick it soon.

Thanks, applied to perf-tools-next, for v7.2.

- Arnaldo

      reply	other threads:[~2026-05-06  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 12:42 [PATCH] perf callchain: Handle multiple address spaces Thomas Richter
2026-04-14 13:13 ` sashiko-bot
2026-04-21 11:10 ` [PATCH Ping ] " Thomas Richter
2026-04-21 16:30 ` [PATCH] " Namhyung Kim
2026-04-29  7:14   ` Thomas Richter
2026-04-30  2:57     ` Namhyung Kim
2026-05-04  9:56       ` Thomas Richter
2026-05-04 23:48         ` Namhyung Kim
2026-05-05  5:50           ` Thomas Richter
2026-05-05 13:04             ` Arnaldo Carvalho de Melo
2026-05-06  0:57               ` Arnaldo Carvalho de Melo [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=afqR-mL5g26ar72N@x1 \
    --to=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=japo@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sumanthk@linux.ibm.com \
    --cc=tmricht@linux.ibm.com \
    /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.