From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Networking <netdev@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Richard Cochran <richardcochran@gmail.com>,
Haren Myneni <haren@linux.ibm.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Donnellan <ajd@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nathan Lynch <nathanl@linux.ibm.com>
Subject: [PATCH v2 3/3] Documentation: ioctl-number: Correct full path to papr-physical-attestation.h
Date: Mon, 14 Jul 2025 08:57:10 +0700 [thread overview]
Message-ID: <20250714015711.14525-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250714015711.14525-1-bagasdotme@gmail.com>
Commit 03c9d1a5a30d93 ("Documentation: Fix description format for
powerpc RTAS ioctls") fixes Sphinx warning by chopping arch/ path
component of papr-physical-attestation.h to fit existing "Include File"
column. Now that the column has been widened just enough for that
header file, add back its arch/ path component.
Fixes: 03c9d1a5a30d ("Documentation: Fix description format for powerpc RTAS ioctls")
Reviewed-by: Haren Myneni <haren@linux.ibm.com>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/userspace-api/ioctl/ioctl-number.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
index a7f729eb0c3694..24c7f480e31057 100644
--- a/Documentation/userspace-api/ioctl/ioctl-number.rst
+++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
@@ -369,7 +369,7 @@ Code Seq# Include File Comments
<mailto:linuxppc-dev@lists.ozlabs.org>
0xB2 06-07 arch/powerpc/include/uapi/asm/papr-platform-dump.h powerpc/pseries Platform Dump API
<mailto:linuxppc-dev@lists.ozlabs.org>
-0xB2 08 powerpc/include/uapi/asm/papr-physical-attestation.h powerpc/pseries Physical Attestation API
+0xB2 08 arch/powerpc/include/uapi/asm/papr-physical-attestation.h powerpc/pseries Physical Attestation API
<mailto:linuxppc-dev@lists.ozlabs.org>
0xB3 00 linux/mmc/ioctl.h
0xB4 00-0F linux/gpio.h <mailto:linux-gpio@vger.kernel.org>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-07-14 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 1:57 [PATCH v2 0/3] ioctl numbers list cleanup for papr-physical-attestation.h Bagas Sanjaya
2025-07-14 1:57 ` [PATCH v2 1/3] Documentation: ioctl-number: Fix linuxppc-dev mailto link Bagas Sanjaya
2025-07-14 1:57 ` [PATCH v2 2/3] Documentation: ioctl-number: Extend "Include File" column width Bagas Sanjaya
2025-07-14 1:57 ` Bagas Sanjaya [this message]
2025-07-14 2:45 ` [PATCH v2 0/3] ioctl numbers list cleanup for papr-physical-attestation.h Madhavan Srinivasan
2025-07-15 20:03 ` Jonathan Corbet
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=20250714015711.14525-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ajd@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=haren@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.