From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Jiri Kosina <jikos@kernel.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-doc@vger.kernel.org, live-patching@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v6 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup
Date: Wed, 20 Jan 2021 16:47:12 +0000 [thread overview]
Message-ID: <20210120164714.16581-1-broonie@kernel.org> (raw)
This series adds a document, mainly written by Mark Rutland, which makes
explicit the requirements for implementing reliable stacktrace in order
to aid architectures adding this feature. It also updates the other
livepatching documents to use automatically generated tables of contents
following review comments on Mark's document.
v6:
- Remove a duplicated "points".
v5:
- Tweaks to the commit message for the new document.
- Convert new and existing documents to autogenerated tables of
contents.
v4:
- Renumber table of contents
v3:
- Incorporated objtool section from Mark.
- Deleted confusing notes about using annotations.
Mark Brown (1):
Documentation: livepatch: Convert to automatically generated contents
Mark Rutland (1):
Documentation: livepatch: document reliable stacktrace
Documentation/livepatch/index.rst | 1 +
Documentation/livepatch/livepatch.rst | 15 +-
Documentation/livepatch/module-elf-format.rst | 10 +-
.../livepatch/reliable-stacktrace.rst | 309 ++++++++++++++++++
4 files changed, 313 insertions(+), 22 deletions(-)
create mode 100644 Documentation/livepatch/reliable-stacktrace.rst
base-commit: 7c53f6b671f4aba70ff15e1b05148b10d58c2837
--
2.20.1
next reply other threads:[~2021-01-20 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 16:47 Mark Brown [this message]
2021-01-20 16:47 ` [PATCH v6 1/2] Documentation: livepatch: Convert to automatically generated contents Mark Brown
2021-01-20 16:47 ` [PATCH v6 2/2] Documentation: livepatch: document reliable stacktrace Mark Brown
2021-01-21 18:52 ` [PATCH v6 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup Jonathan Corbet
2021-01-22 10:59 ` Jiri Kosina
2021-01-26 10:50 ` Jiri Kosina
2021-01-27 10:32 ` Miroslav Benes
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=20210120164714.16581-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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;
as well as URLs for NNTP newsgroup(s).