linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@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>,
	Haren Myneni <haren@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: Re: [PATCH v2 0/3] ioctl numbers list cleanup for papr-physical-attestation.h
Date: Mon, 14 Jul 2025 08:15:58 +0530	[thread overview]
Message-ID: <926d9ce3-04fc-4055-b5e5-fda8772e3da8@linux.ibm.com> (raw)
In-Reply-To: <20250714015711.14525-1-bagasdotme@gmail.com>



On 7/14/25 7:27 AM, Bagas Sanjaya wrote:
> Hi,
> 
> This is the cleanup series following up from 03c9d1a5a30d93 ("Documentation:
> Fix description format for powerpc RTAS ioctls"). It is based on docs-next
> tree. The end result should be the same as my previous fixup patch [1].
> 
> Enjoy!
> 

for powerpc changes
Acked-by: Madhavan Srinivasan <maddy@linux.ibm.com>


> Changes since v1 (RESEND) [2]:
> 
>   * Add Fixes: and Reviewed-by: trailers (Haren)
>   * Expand tabs for uapi/misc/amd-apml.h to match other entries
> 
> Jon: Would you like to apply this series on docs-next or should powerpc
> folks handle it?
> 
> [1]: https://lore.kernel.org/linuxppc-dev/20250429130524.33587-2-bagasdotme@gmail.com/
> [2]: https://lore.kernel.org/lkml/20250708004334.15861-1-bagasdotme@gmail.com/
> 
> Bagas Sanjaya (3):
>   Documentation: ioctl-number: Fix linuxppc-dev mailto link
>   Documentation: ioctl-number: Extend "Include File" column width
>   Documentation: ioctl-number: Correct full path to
>     papr-physical-attestation.h
> 
>  .../userspace-api/ioctl/ioctl-number.rst      | 516 +++++++++---------
>  1 file changed, 258 insertions(+), 258 deletions(-)
> 
> 
> base-commit: f55b3ca3cf1d1652c4b3481b671940461331d69f


  parent reply	other threads:[~2025-07-14  2:46 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 ` [PATCH v2 3/3] Documentation: ioctl-number: Correct full path to papr-physical-attestation.h Bagas Sanjaya
2025-07-14  2:45 ` Madhavan Srinivasan [this message]
2025-07-15 20:03 ` [PATCH v2 0/3] ioctl numbers list cleanup for papr-physical-attestation.h 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=926d9ce3-04fc-4055-b5e5-fda8772e3da8@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=ajd@linux.ibm.com \
    --cc=bagasdotme@gmail.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=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 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).