From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: aleszlucero@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] staging: octeon: fix probe error path and pow_send_list matching
Date: Fri, 20 Nov 2026 08:20:26 +0100 [thread overview]
Message-ID: <2026112003-briar-freckles-de3b@gregkh> (raw)
In-Reply-To: <20261111-octeon-init-pipeline-v1-v4-0-5b4f8e613ae1@gmail.com>
On Wed, Nov 11, 2026 at 09:48:31PM -0600, Oscar Alejandro Sánchez Lucero via B4 Relay wrote:
> Fixed two bugs in drivers/staging/octeon/ethernet.c:
>
> 1. Call cvmx_pko_disable() in the cvm_oct_probe() error path to match the
> teardown sequence in cvm_oct_remove().
> 2. Split pow_send_list on commas using strsep() instead of matching
> substrings with strstr().
>
> Oscar Alejandro Sánchez Lucero (2):
> staging: octeon: disable PKO before device removal in probe error path
> staging: octeon: match exact interface names in pow_send_list
>
> Signed-off-by: Oscar Alejandro Sánchez Lucero <aleszlucero@gmail.com>
> ---
> Changes in v4:
> - Build tested on mips64 (cavium_octeon_defconfig) with W=1.
> - Link to v3: https://lore.kernel.org/r/20261111-octeon-init-pipeline-v1-v3-0-e5581974fae4@gmail.com
Without real hardware for you to test these changes on, I'm not going to
be able to accept any of your changes, sorry.
greg k-h
prev parent reply other threads:[~2026-11-20 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 3:48 [PATCH v4 0/2] staging: octeon: fix probe error path and pow_send_list matching Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-12 3:48 ` [PATCH v4 1/2] staging: octeon: disable PKO before device removal in probe error path Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-12 3:48 ` [PATCH v4 2/2] staging: octeon: match exact interface names in pow_send_list Oscar Alejandro Sánchez Lucero via B4 Relay
2026-11-20 7:20 ` Greg Kroah-Hartman [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=2026112003-briar-freckles-de3b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aleszlucero@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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