From: Steven Rostedt <rostedt@goodmis.org>
To: Philipp Rudo <prudo@redhat.com>
Cc: Ricardo Ribalda <ribalda@chromium.org>,
Eric Biederman <ebiederm@xmission.com>,
Jonathan Corbet <corbet@lwn.net>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
Ross Zwisler <zwisler@kernel.org>,
linux-doc@vger.kernel.org,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: [PATCH v1 2/2] kexec: Introduce kexec_reboot_disabled
Date: Mon, 28 Nov 2022 18:37:18 -0500 [thread overview]
Message-ID: <20221128183718.46c08bb5@gandalf.local.home> (raw)
In-Reply-To: <20221128172347.629a75c2@rotkaeppchen>
On Mon, 28 Nov 2022 17:28:55 +0100
Philipp Rudo <prudo@redhat.com> wrote:
> To be honest I don't think we make a progress here at the moment. I
> would like to hear from others what they think about this.
Not sure if you missed my reply.
https://lore.kernel.org/all/20221128114200.72b3e2fe@gandalf.local.home/
-- Steve
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-11-28 23:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 13:18 [PATCH v1 0/2] kexec: Add new toogle to disable kexec_reboot Ricardo Ribalda
2022-11-14 13:18 ` [PATCH v1 1/2] Documentation: sysctl: Correct kexec_load_disabled Ricardo Ribalda
2022-11-23 9:47 ` Baoquan He
2022-11-14 13:18 ` [PATCH v1 2/2] kexec: Introduce kexec_reboot_disabled Ricardo Ribalda
2022-11-17 15:06 ` Philipp Rudo
2022-11-17 15:15 ` Ricardo Ribalda
2022-11-21 14:09 ` Philipp Rudo
2022-11-23 8:58 ` Ricardo Ribalda
2022-11-24 11:40 ` Philipp Rudo
2022-11-24 12:52 ` Ricardo Ribalda
2022-11-24 15:01 ` Philipp Rudo
2022-11-24 22:32 ` Ricardo Ribalda
2022-11-28 16:28 ` Philipp Rudo
2022-11-28 23:37 ` Steven Rostedt [this message]
2022-11-28 16:42 ` Steven Rostedt
2022-11-29 13:44 ` Philipp Rudo
2022-11-29 14:32 ` Steven Rostedt
2022-12-12 21:43 ` Ricardo Ribalda
2022-11-23 13:49 ` Baoquan He
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=20221128183718.46c08bb5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=joel@joelfernandes.org \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prudo@redhat.com \
--cc=ribalda@chromium.org \
--cc=senozhatsky@chromium.org \
--cc=zwisler@kernel.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