live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mark Brown <broonie@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	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
Subject: Re: [PATCH v6 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup
Date: Fri, 22 Jan 2021 11:59:09 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2101221158450.5622@cbobk.fhfr.pm> (raw)
In-Reply-To: <20210121115226.565790ef@lwn.net>

On Thu, 21 Jan 2021, Jonathan Corbet 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.
> 
> So...is this deemed ready and, if so, do you want it to go through the
> docs tree or via some other path?

I am planning to take it through livepatching tree unless there are any 
additional last-minutes comments.

Thanks,

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2021-01-22 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 16:47 [PATCH v6 0/2] Documentation: livepatch: Document reliable stacktrace and minor cleanup Mark Brown
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 [this message]
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=nycvar.YFH.7.76.2101221158450.5622@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --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).