From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-perf-users@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Petlan <mpetlan@redhat.com>,
Veronika Molnarova <vmolnaro@redhat.com>,
Suren Baghdasaryan <surenb@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 0/2] tracing: gfp: Fix regression of printing GFP flags in user space tracing tooling
Date: Thu, 16 Jan 2025 16:48:40 -0500 [thread overview]
Message-ID: <20250116164840.5f278bbc@gandalf.local.home> (raw)
In-Reply-To: <20250116214123.917928229@goodmis.org>
On Thu, 16 Jan 2025 16:41:23 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> This fixes a regression that was brought up last year[1], but due
> to missing a response it was forgotten about.
Note, these were only tested by building and booting the kernel to see if
the gfp_flags have been fixed. I did not run this through my normal tests.
I can run them, and if I get an Ack from the memory maintainers I could
push them through my tree.
I would also like to have those that reported the issue confirm this fixes
the problem for them and they give me a "Tested-by".
-- Steve
prev parent reply other threads:[~2025-01-16 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 21:41 Steven Rostedt
2025-01-16 21:41 ` [PATCH v2 1/2] tracing: gfp: Fix the GFP enum values shown for user space tracing tools Steven Rostedt
2025-01-16 21:41 ` [PATCH v2 2/2] tracing: gfp: Remove duplication of recording GFP flags Steven Rostedt
2025-01-16 21:48 ` 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=20250116164840.5f278bbc@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mpetlan@redhat.com \
--cc=surenb@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vmolnaro@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox