mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Jakub Sitnicki <jakub@cloudflare.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	x86@kernel.org
Subject: Re: [tip: perf/core] libbpf: Change has_nop_combo to work on top of nop10
Date: Sat, 4 Jul 2026 10:58:58 +0200	[thread overview]
Message-ID: <akjLUnu9o1OHGngA@gmail.com> (raw)
In-Reply-To: <178308930864.3843924.6189769470992755436.tip-bot2@tip-bot2>


* tip-bot2 for Jiri Olsa <tip-bot2@linutronix.de> wrote:

> The following commit has been merged into the perf/core branch of tip:
> 
> Commit-ID:     c005cd83b07a0ea1ffe3115f321ed3190fb3894b
> Gitweb:        https://git.kernel.org/tip/c005cd83b07a0ea1ffe3115f321ed3190fb3894b
> Author:        Jiri Olsa <jolsa@kernel.org>
> AuthorDate:    Fri, 03 Jul 2026 13:49:10 +02:00
> Committer:     Peter Zijlstra <peterz@infradead.org>
> CommitterDate: Fri, 03 Jul 2026 16:30:36 +02:00
> 
> libbpf: Change has_nop_combo to work on top of nop10
> 
> We now expect nop combo with 10 bytes nop instead of 5 bytes nop,
> fixing has_nop_combo to reflect that.
> 
> Fixes: 41a5c7df4466 ("libbpf: Add support to detect nop,nop5 instructions combo for usdt probe")
> Fixes: af734a7ddb4e ("uprobes/x86: Move optimized uprobe from nop5 to nop10")

The second Fixes tag is bogus in this commit too - I fixed it to:

  554ba38456da ("uprobes/x86: Move optimized uprobe from nop5 to nop10")

Thanks,

	Ingo

  reply	other threads:[~2026-07-04  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260703114917.238144-7-jolsa@kernel.org>
2026-07-03 14:35 ` tip-bot2 for Jiri Olsa
2026-07-04  8:58   ` Ingo Molnar [this message]
2026-07-04  9:00 ` tip-bot2 for Jiri Olsa

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=akjLUnu9o1OHGngA@gmail.com \
    --to=mingo@kernel.org \
    --cc=andrii@kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.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®