From: Steven Rostedt <rostedt@goodmis.org>
To: Kees Cook <keescook@chromium.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Tony Luck" <tony.luck@intel.com>,
"Anton Vorontsov" <anton@enomsg.org>,
linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>,
kernel@pengutronix.de, "Colin Cross" <ccross@android.com>
Subject: Re: [PATCH] pstore/ftrace: add a kernel parameter to start pstore recording
Date: Mon, 29 Nov 2021 17:40:25 -0500 [thread overview]
Message-ID: <20211129174025.70b5718f@gandalf.local.home> (raw)
In-Reply-To: <202111161259.D0972333@keescook>
On Tue, 16 Nov 2021 13:00:07 -0800
Kees Cook <keescook@chromium.org> wrote:
> On Tue, Nov 16, 2021 at 12:37:05PM -0500, Steven Rostedt wrote:
> > On Tue, 16 Nov 2021 18:28:35 +0100
> > Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
> >
> > > > Is this still needed? It's still in my internal patchwork, and I haven't
> > > > seen any responses.
> > >
> > > I didn't see any responses either, and unless someone else implemented
> > > something similar somewhere else, it's still needed.
> > >
> > > The change was actually useful to debug a clk problem, where the machine
> > > freezed when a certain driver was loaded.
> >
> > Perhaps I should ask this. Would anyone object if I just take this change
> > through my tree for the next merge window?
>
> If you can Ack it, I'll take it via the pstore tree; I've got a few
> other things that will likely need to go in for the next merge window
> too.
>
I've must have missed this.
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2021-11-29 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:21 [PATCH] pstore/ftrace: add a kernel parameter to start pstore recording Uwe Kleine-König
2021-11-16 17:06 ` Steven Rostedt
2021-11-16 17:28 ` Uwe Kleine-König
2021-11-16 17:37 ` Steven Rostedt
2021-11-16 20:52 ` Uwe Kleine-König
2021-11-16 21:00 ` Kees Cook
2021-11-29 22:40 ` Steven Rostedt [this message]
2021-11-18 18:08 ` Kees Cook
2021-11-18 18:31 ` Kees Cook
2021-11-19 7:25 ` Uwe Kleine-König
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=20211129174025.70b5718f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tony.luck@intel.com \
--cc=u.kleine-koenig@pengutronix.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 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.