From: Haren Myneni <haren@linux.ibm.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
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>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Donnellan <ajd@linux.ibm.com>
Subject: Re: [PATCH RESEND 3/3] Documentation: ioctl-number: Correct full path to papr-physical-attestation.h
Date: Mon, 07 Jul 2025 23:24:34 -0700 [thread overview]
Message-ID: <a5c6173f3109dac14e43c30f6483afe19573870f.camel@linux.ibm.com> (raw)
In-Reply-To: <20250708004334.15861-4-bagasdotme@gmail.com>
On Tue, 2025-07-08 at 07:43 +0700, Bagas Sanjaya wrote:
> 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")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks for fixing.
Reviewed-by: Haren Myneni <haren@linux.ibm.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 b45f5d857a00b6..5aa09865b3aa0f 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>
prev parent reply other threads:[~2025-07-08 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 0:43 [PATCH RESEND 0/3] ioctl numbers list cleanup for papr-physical-attestation.h Bagas Sanjaya
2025-07-08 0:43 ` [PATCH RESEND 1/3] Documentation: ioctl-number: Fix linuxppc-dev mailto link Bagas Sanjaya
2025-07-08 6:23 ` Haren Myneni
2025-07-14 1:04 ` Bagas Sanjaya
2025-07-08 0:43 ` [PATCH RESEND 2/3] Documentation: ioctl-number: Extend "Include File" column width Bagas Sanjaya
2025-07-08 6:26 ` Haren Myneni
2025-07-08 0:43 ` [PATCH RESEND 3/3] Documentation: ioctl-number: Correct full path to papr-physical-attestation.h Bagas Sanjaya
2025-07-08 6:24 ` Haren Myneni [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=a5c6173f3109dac14e43c30f6483afe19573870f.camel@linux.ibm.com \
--to=haren@linux.ibm.com \
--cc=ajd@linux.ibm.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@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 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).