All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Eva Kurchatova <eva.kurchatova@virtuozzo.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [GIT PULL] tracing: Fixes for 7.1
Date: Sat, 6 Jun 2026 14:58:59 -0700	[thread overview]
Message-ID: <20260606215859.GA2996810@ax162> (raw)
In-Reply-To: <20260605155804.GA3472545@ax162>

On Fri, Jun 05, 2026 at 08:58:10AM -0700, Nathan Chancellor wrote:
> On Thu, Jun 04, 2026 at 08:47:55AM -0400, Steven Rostedt wrote:
> > commit 0652a3daa78723f955b1ebeb621665ce72bec53e
> > Author: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
> > Date:   Wed Jun 3 18:31:42 2026 +0300
> > 
> >     tracing: Fix CFI violation in probestub being called by tprobes
...
> 
> This needs a build fix, as ARCH=arm allmodconfig is now broken with
> Clang.
> 
>   https://lore.kernel.org/20260604-tracing-fix-cfi-h-build-error-v1-1-b27015390901@kernel.org/

Linus, could you apply this directly? Other folks have already noticed
this breakage:

  https://android-review.googlesource.com/c/kernel/common/+/4105881

-- 
Cheers,
Nathan

  reply	other threads:[~2026-06-06 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 12:47 [GIT PULL] tracing: Fixes for 7.1 Steven Rostedt
2026-06-04 22:12 ` pr-tracker-bot
2026-06-05 15:58 ` Nathan Chancellor
2026-06-06 21:58   ` Nathan Chancellor [this message]
2026-06-06 22:09     ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2026-05-21 22:08 Steven Rostedt
2026-05-22 14:26 ` pr-tracker-bot
2026-05-17 13:17 Steven Rostedt
2026-05-17 19:28 ` pr-tracker-bot

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=20260606215859.GA2996810@ax162 \
    --to=nathan@kernel.org \
    --cc=eva.kurchatova@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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 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.