From: Randy Dunlap <rdunlap@infradead.org>
To: Karl Mehltretter <kmehltretter@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Haren Myneni <haren@us.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] docs: powerpc: vas-api: Use the uapi structure name in the example
Date: Sat, 5 Sep 2026 10:36:53 -0700 [thread overview]
Message-ID: <491168f4-64f4-4781-b0f7-4eda2e899dc4@infradead.org> (raw)
In-Reply-To: <20260905104313.43620-1-kmehltretter@gmail.com>
On 9/5/26 3:43 AM, Karl Mehltretter wrote:
> struct vas_setup_attr does not exist; the name is struct
> vas_tx_win_open_attr.
>
> Use struct vas_tx_win_open_attr.
>
> Fixes: c12e38b1d52e ("Documentation/powerpc: VAS API")
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/arch/powerpc/vas-api.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/arch/powerpc/vas-api.rst b/Documentation/arch/powerpc/vas-api.rst
> index 1d0d055356e3..00d98cfd95c9 100644
> --- a/Documentation/arch/powerpc/vas-api.rst
> +++ b/Documentation/arch/powerpc/vas-api.rst
> @@ -265,7 +265,7 @@ Simple example
> {
> int rc, fd;
> void *addr;
> - struct vas_setup_attr txattr;
> + struct vas_tx_win_open_attr txattr;
>
> fd = open("/dev/crypto/nx-gzip", O_RDWR);
> if (fd < 0) {
--
~Randy
next prev parent reply other threads:[~2026-09-05 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 10:43 [PATCH] docs: powerpc: vas-api: Use the uapi structure name in the example Karl Mehltretter
2026-09-05 17:36 ` Randy Dunlap [this message]
2026-09-06 2:57 ` Ritesh Harjani
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=491168f4-64f4-4781-b0f7-4eda2e899dc4@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=haren@us.ibm.com \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=skhan@linuxfoundation.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