From: Klara Modin <klarasmodin@gmail.com>
To: Prashant Rahul <prashantrahul23@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] staging: octeon: Improve initialization error handling
Date: Fri, 3 Jul 2026 12:30:59 +0200 [thread overview]
Message-ID: <akePJ0yt9APAyCNX@soda.int.kasm.eu> (raw)
In-Reply-To: <20260702-staging-driver-octeon-panic-v2-0-2c2b6ae086dd@gmail.com>
On 2026-07-02 12:36:13 +0530, Prashant Rahul wrote:
> Hi all,
>
> The TX and RX initialization paths currently call panic() on some
> initialization failures. Instead, these failures should be reported back
> to the probe function so that it can unwind any resources acquired during
> initialization and fail gracefully.
>
> This series replaces those panic() calls with proper error logging, propagates
> the errors to the probe function, and adds the necessary cleanup to avoid
> leaving the driver in a partially initialized state. I have not tested
> these changes as I do not own this hardware.
>
> This is my first time working with drivers, so please let me know if I
> have made any mistakes.
>
> Thank you! :3
>
> Signed-off-by: Prashant Rahul <prashantrahul23@gmail.com>
Tested-by: Klara Modin <klarasomdin@gmail.com>
> ---
> Changes in v2:
> - ethernet.c: remove unnecessary curly braces around single line for-loop
> - ethernet.c: dont mark cvm_oct_remove_device as inline
> - ethernet.c: remove unnecessary call to cvmx_pko_disable as cvmx_pko_shutdown
> already does that.
> - cover: specify no testing
>
> - Link to v1: https://lore.kernel.org/r/20260628-staging-driver-octeon-panic-v1-0-fe8c34989254@gmail.com
>
> ---
> Prashant Rahul (4):
> staging: octeon: factor out device removal into a helper
> staging: octeon: Propagate rx initialization failures
> staging: octeon: Propagate tx initialization failures
> staging: octeon: handle rx/tx initialization failures in probe
>
> drivers/staging/octeon/ethernet-rx.c | 18 ++++++----
> drivers/staging/octeon/ethernet-rx.h | 2 +-
> drivers/staging/octeon/ethernet-tx.c | 17 +++++-----
> drivers/staging/octeon/ethernet-tx.h | 2 +-
> drivers/staging/octeon/ethernet.c | 66 ++++++++++++++++++++++++++++--------
> 5 files changed, 74 insertions(+), 31 deletions(-)
> ---
> base-commit: 4e5dfb7c84012007c3c7061126491bbc92d71bf1
> change-id: 20260625-staging-driver-octeon-panic-2602ed8d5d67
>
> Best regards,
> --
> Prashant Rahul <prashantrahul23@gmail.com>
>
prev parent reply other threads:[~2026-07-03 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 7:06 [PATCH v2 0/4] staging: octeon: Improve initialization error handling Prashant Rahul
2026-07-02 7:06 ` [PATCH v2 1/4] staging: octeon: factor out device removal into a helper Prashant Rahul
2026-07-02 7:06 ` [PATCH v2 2/4] staging: octeon: Propagate rx initialization failures Prashant Rahul
2026-07-02 7:06 ` [PATCH v2 3/4] staging: octeon: Propagate tx " Prashant Rahul
2026-07-02 7:06 ` [PATCH v2 4/4] staging: octeon: handle rx/tx initialization failures in probe Prashant Rahul
2026-07-03 10:30 ` Klara Modin [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=akePJ0yt9APAyCNX@soda.int.kasm.eu \
--to=klarasmodin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=prashantrahul23@gmail.com \
--cc=shuah@kernel.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