From: Sasha Levin <sashal@kernel.org>
To: alexevgmart@gmail.com, stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
karolherbst@gmail.com, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, mhiramat@kernel.org,
mingo@kernel.org, nouveau@lists.freedesktop.org,
ppaalanen@gmail.com, rostedt@goodmis.org, tglx@linutronix.de,
Ingo Molnar <mingo@elte.hu>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5.15/6.1/6.6 0/2] tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions
Date: Mon, 7 Sep 2026 20:53:51 -0400 [thread overview]
Message-ID: <2026-09-07-daily-reply-0012-mmiotrace-v2-3trees@kernel.org> (raw)
In-Reply-To: <20260907163919.183961-1-alexevgmart@gmail.com>
> Masami Hiramatsu (Google) (1):
> tracing/mmiotrace: Add NULL check for mmio_trace_array in logging
> functions
>
> Steven Rostedt (1):
> tracing/mmiotrace: Remove reference to unused per CPU data pointer
Queued for 6.6, 6.1 and 5.15, thanks. Good catch adding the
prerequisite.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-09-08 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260902122613.442176-1-alexevgmart@gmail.com>
2026-09-07 16:39 ` [PATCH v2 5.15/6.1/6.6 0/2] tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions Alexander Martyniuk
2026-09-07 16:39 ` [PATCH v2 5.15/6.1/6.6 1/2] tracing/mmiotrace: Remove reference to unused per CPU data pointer Alexander Martyniuk
2026-09-07 16:39 ` [PATCH v2 5.15/6.1/6.6 2/2] tracing/mmiotrace: Add NULL check for mmio_trace_array in logging functions Alexander Martyniuk
2026-09-08 0:53 ` Sasha Levin [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=2026-09-07-daily-reply-0012-mmiotrace-v2-3trees@kernel.org \
--to=sashal@kernel.org \
--cc=alexevgmart@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=karolherbst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mhiramat@kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ppaalanen@gmail.com \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).