From: Jonathan Corbet <corbet@lwn.net>
To: Nicolas Saenz Julienne <nsaenzju@redhat.com>,
tglx@linutronix.de, mark.rutland@arm.com, paulmck@kernel.org
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, rcu@vger.kernel.org,
peterz@infradead.org, mtosatti@redhat.com, frederic@kernel.org,
Nicolas Saenz Julienne <nsaenzju@redhat.com>
Subject: Re: [PATCH v4 1/2] Documentation: Fill the gaps about entry/noinstr constraints
Date: Thu, 27 Jan 2022 11:33:36 -0700 [thread overview]
Message-ID: <877dalrptr.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220110105044.94423-1-nsaenzju@redhat.com>
Nicolas Saenz Julienne <nsaenzju@redhat.com> writes:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> The entry/exit handling for exceptions, interrupts, syscalls and KVM is
> not really documented except for some comments.
>
> Fill the gaps.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de
> Co-developed-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
> Reviewed-by: Mark Rutland <mark.rutland@arm.com>
> Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
>
Both patches applied, thanks.
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-01-27 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 10:50 [PATCH v4 1/2] Documentation: Fill the gaps about entry/noinstr constraints Nicolas Saenz Julienne
2022-01-10 10:50 ` [PATCH v4 2/2] Documentation: core-api: entry: Add comments about nesting Nicolas Saenz Julienne
2022-01-10 18:01 ` Paul E. McKenney
2022-01-21 14:55 ` Frederic Weisbecker
2022-01-21 14:47 ` [PATCH v4 1/2] Documentation: Fill the gaps about entry/noinstr constraints Frederic Weisbecker
2022-01-27 18:33 ` Jonathan Corbet [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=877dalrptr.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=frederic@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mtosatti@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).