From: Aditya Gupta <adityag@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, Gautam Menghani <gautam@linux.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] docs: fix typo in xive doc
Date: Fri, 29 Aug 2025 09:35:15 +0530 [thread overview]
Message-ID: <112c5fa8-65e4-474c-9e4c-87322e6259d8@linux.ibm.com> (raw)
In-Reply-To: <cd274edb-fd19-4e06-806c-cc8f30b6f32f@redhat.com>
On 27/08/25 13:33, Thomas Huth wrote:
> On 27/08/2025 07.32, Aditya Gupta wrote:
>> "Interrupt Pending Buffer" IPB, which got written as IBP due to typo.
>>
>> The "IPB" register is also mentioned in same doc multiple times.
>>
>> Signed-off-by: Aditya Gupta <adityag@linux.ibm.com>
>> ---
>> docs/specs/ppc-xive.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/docs/specs/ppc-xive.rst b/docs/specs/ppc-xive.rst
>> index 83d43f658b90..968cc760d466 100644
>> --- a/docs/specs/ppc-xive.rst
>> +++ b/docs/specs/ppc-xive.rst
>> @@ -157,7 +157,7 @@ Interrupt flow from an O/S perspective
>> After an event data has been enqueued in the O/S Event Queue, the
>> IVPE
>> raises the bit corresponding to the priority of the pending interrupt
>> -in the register IBP (Interrupt Pending Buffer) to indicate that an
>> +in the register IPB (Interrupt Pending Buffer) to indicate that an
>> event is pending in one of the 8 priority queues. The Pending
>> Interrupt Priority Register (PIPR) is also updated using the IPB. This
>> register represent the priority of the most favored pending
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
Thanks for the tag, Thomas !
- Aditya G
prev parent reply other threads:[~2025-08-30 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250827053228.519707-1-adityag@linux.ibm.com>
2025-08-27 8:03 ` [PATCH] docs: fix typo in xive doc Thomas Huth
2025-08-29 4:05 ` Aditya Gupta [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=112c5fa8-65e4-474c-9e4c-87322e6259d8@linux.ibm.com \
--to=adityag@linux.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.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).