public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Geoff Levand <geoff@infradead.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <chleroy@kernel.org>
Subject: Re: [PATCH] powerpc/ps3: spu.c: fix enum and Return kernel-doc warnings
Date: Wed,  8 Apr 2026 09:59:00 +0530	[thread overview]
Message-ID: <177562236428.1381144.14186364589664426663.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260225055328.249204-1-rdunlap@infradead.org>

On Tue, 24 Feb 2026 21:53:28 -0800, Randy Dunlap wrote:
> Fix enum and function return value kernel-doc warnings:
> 
> Warning: spu.c:36 Excess enum value '%spe_type_logical' description in 'spe_type'
> Warning: spu.c:78 Excess enum value '%spe_ex_state_unexecutable' description in 'spe_ex_state'
> Warning: spu.c:78 Excess enum value '%spe_ex_state_executable' description in 'spe_ex_state'
> Warning: spu.c:78 Excess enum value '%spe_ex_state_executed' description in 'spe_ex_state'
> Warning: spu.c:190 No description found for return value of 'setup_areas'
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/ps3: spu.c: fix enum and Return kernel-doc warnings
      https://git.kernel.org/powerpc/c/26d76caac47f44b3ee4cdf080614bbee07713007

cheers


  reply	other threads:[~2026-04-08  4:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  5:53 [PATCH] powerpc/ps3: spu.c: fix enum and Return kernel-doc warnings Randy Dunlap
2026-04-08  4:29 ` Madhavan Srinivasan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-14  3:12 Randy Dunlap

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=177562236428.1381144.14186364589664426663.b4-ty@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=geoff@infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=rdunlap@infradead.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