From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, 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>,
linux-doc@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: [PATCH v5 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup
Date: Mon, 18 Jan 2021 12:00:46 -0600 [thread overview]
Message-ID: <20210118175927.jjscqq24jbtqprc7@treble> (raw)
In-Reply-To: <20210118173954.36577-1-broonie@kernel.org>
On Mon, Jan 18, 2021 at 05:39:52PM +0000, Mark Brown wrote:
> 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.
>
> 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
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
prev parent reply other threads:[~2021-01-18 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 17:39 [PATCH v5 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup Mark Brown
2021-01-18 17:39 ` [PATCH v5 1/2] Documentation: livepatch: Convert to automatically generated contents Mark Brown
2021-01-18 17:39 ` [PATCH v5 2/2] Documentation: livepatch: document reliable stacktrace Mark Brown
2021-01-18 19:25 ` Randy Dunlap
2021-01-18 18:00 ` Josh Poimboeuf [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=20210118175927.jjscqq24jbtqprc7@treble \
--to=jpoimboe@redhat.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@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