From: David Gibson <david@gibson.dropbear.id.au>
To: Gustavo Romero <gromero@linux.ibm.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org
Subject: Re: [PATCH] ppc/xive: Fix some typos in comments
Date: Thu, 23 Jul 2020 10:45:45 +1000 [thread overview]
Message-ID: <20200723004545.GF5513@umbus.fritz.box> (raw)
In-Reply-To: <1595461434-27725-1-git-send-email-gromero@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
On Wed, Jul 22, 2020 at 07:43:54PM -0400, Gustavo Romero wrote:
> Fix some typos in comments about code modeling coalescing points in the
> XIVE routing engine (IVRE).
>
> Signed-off-by: Gustavo Romero <gromero@linux.ibm.com>
Applied to ppc-for-5.2.
> ---
> hw/intc/xive.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/intc/xive.c b/hw/intc/xive.c
> index 9a16243..9b55e03 100644
> --- a/hw/intc/xive.c
> +++ b/hw/intc/xive.c
> @@ -1502,7 +1502,7 @@ static bool xive_presenter_notify(XiveFabric *xfb, uint8_t format,
>
> /*
> * Notification using the END ESe/ESn bit (Event State Buffer for
> - * escalation and notification). Profide futher coalescing in the
> + * escalation and notification). Provide further coalescing in the
> * Router.
> */
> static bool xive_router_end_es_notify(XiveRouter *xrtr, uint8_t end_blk,
> @@ -1581,7 +1581,7 @@ static void xive_router_end_notify(XiveRouter *xrtr, uint8_t end_blk,
>
> /*
> * Check the END ESn (Event State Buffer for notification) for
> - * even futher coalescing in the Router
> + * even further coalescing in the Router
> */
> if (!xive_end_is_notify(&end)) {
> /* ESn[Q]=1 : end of notification */
> @@ -1660,7 +1660,7 @@ do_escalation:
>
> /*
> * Check the END ESe (Event State Buffer for escalation) for even
> - * futher coalescing in the Router
> + * further coalescing in the Router
> */
> if (!xive_end_is_uncond_escalation(&end)) {
> /* ESe[Q]=1 : end of notification */
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-07-23 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 23:43 [PATCH] ppc/xive: Fix some typos in comments Gustavo Romero
2020-07-23 0:45 ` David Gibson [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=20200723004545.GF5513@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=gromero@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).