From: Greg KH <gregkh@linuxfoundation.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: tsbogend@alpha.franken.de, len.bao@gmx.us,
yoelvisoliveros@gmail.com, error27@gmail.com,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v4] staging: octeon: remove SPI, POW, and PKO typedef enums
Date: Sun, 26 Apr 2026 20:55:46 +0200 [thread overview]
Message-ID: <2026042615-ambulance-upright-3041@gregkh> (raw)
In-Reply-To: <20260418230344.44242-1-m32285159@gmail.com>
On Sat, Apr 18, 2026 at 06:03:44PM -0500, Maxwell Doose wrote:
> This patch removes custom typedef enums and replaces them with standard
> enums to address the "General code review and cleanup" task in TODO.
>
> The following enums are affected:
>
> - cvmx_spi_mode_t (now enum cvmx_spi_mode)
> - cvmx_pow_wait_t (now enum cvmx_pow_wait)
> - cvmx_pko_lock_t (now enum cvmx_pko_lock)
> - cvmx_pko_status_t (now enum cvmx_pko_status)
>
> This patch aligns the octeon codebase more closely with the Linux kernel
> code style, and will address the "cleanup" task in TODO.
>
> Signed-off-by: Maxwell Doose <m32285159@gmail.com>
> ---
> v2:
> - Appended "_e" to enum cvmx_helper_interface_mode to prevent namespace
> collisions with a struct of the same name
> - Fixed errors that were indirect results of the namespace collisions
How was this tested given that the previous ones all were not?
Also, this should be one commit per enum, right? Why not make this a
patch series?
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-27 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 23:03 [PATCH v4] staging: octeon: remove SPI, POW, and PKO typedef enums Maxwell Doose
2026-04-26 18:55 ` Greg KH [this message]
2026-04-27 4:46 ` Maxwell Doose
2026-04-27 9:00 ` Dan Carpenter
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=2026042615-ambulance-upright-3041@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=error27@gmail.com \
--cc=len.bao@gmx.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=m32285159@gmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=yoelvisoliveros@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