live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	linux-kernel@vger.kernel.org, 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,
	linux-doc@vgert.kernel.org
Subject: Re: [PATCH v3] Documentation: livepatch: document reliable stacktrace
Date: Fri, 15 Jan 2021 16:47:18 +0000	[thread overview]
Message-ID: <20210115164718.GE44111@C02TD0UTHF1T.local> (raw)
In-Reply-To: <20210115142446.13880-1-broonie@kernel.org>

Hi Mark,

On Fri, Jan 15, 2021 at 02:24:46PM +0000, Mark Brown wrote:
> +.. Table of Contents:
> +
> +    1. Introduction
> +    2. Requirements
> +    3. Considerations
> +       3.1 Identifying successful termination
> +       3.2 Identifying unwindable code
> +       3.3 Unwinding across interrupts and exceptions
> +       3.4 Rewriting of return addresses
> +       3.5 Obscuring of return addresses
> +       3.6 Link register unreliability
>

It looks like we forgot to update this with the addition of the new
section 3, so this needs a trivial update to add that and fix the
numbering.

Otherwise this looks good; thanks for taking this off my hands! :)

Mark.

  parent reply	other threads:[~2021-01-15 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:24 [PATCH v3] Documentation: livepatch: document reliable stacktrace Mark Brown
2021-01-15 15:16 ` Josh Poimboeuf
2021-01-15 16:47 ` Mark Rutland [this message]
2021-01-15 17:12   ` Mark Brown
2021-01-15 17:20     ` Jonathan Corbet
2021-01-18 12:21       ` Mark Rutland

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=20210115164718.GE44111@C02TD0UTHF1T.local \
    --to=mark.rutland@arm.com \
    --cc=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-doc@vgert.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --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).