mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Helge Deller <deller@gmx.de>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	linux-kernel@vger.kernel.org,
	Sven Schnelle <svens@stackframe.org>,
	linux-trace-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] parisc/ftrace: Fix function graph tracing disablement
Date: Thu, 10 Oct 2024 16:33:13 -0400	[thread overview]
Message-ID: <20241010163313.631e84bd@gandalf.local.home> (raw)
In-Reply-To: <f2dd3a74-cd3d-4277-904d-223a8b393d56@gmx.de>

On Thu, 10 Oct 2024 22:25:13 +0200
Helge Deller <deller@gmx.de> wrote:
> 
> Actually I do, and yes we have users.
> Of course in reality that's "fun" users and not "productive" usage.

We welcome those "fun" users as well!

> 
>  From programming perspective parisc is quite interesting since it
> has an upwards-growing stack, limited ways of atomic ops,
> and some awkward cache dependencies, so I regularly find
> issues in generic Linux code which would not be found otherwise.
> 
> > I still see some git activity in arch/parisc, so apparently so...
> >
> > I only stumbled on this by accident (code inspection) while making
> > another unrelated change.  
> 
> Thanks for your patch!
> I'll apply it in my for-next git tree and push upstream at some point
> (unless someone else takes it before me).

For architecture patches like this, even if it is obvious, I rather it go
through them, as I wouldn't even compile test it.

Please take it through your tree.

Thanks,

-- Steve


      reply	other threads:[~2024-10-10 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 21:32 Josh Poimboeuf
2024-10-10 19:48 ` Steven Rostedt
2024-10-10 19:56   ` Josh Poimboeuf
2024-10-10 20:25     ` Helge Deller
2024-10-10 20:33       ` Steven Rostedt [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=20241010163313.631e84bd@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=deller@gmx.de \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=svens@stackframe.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®