From: Mark Adamenko <marusik.adamenko@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: replace BUG() with WARN_ON_ONCE() in cvn_oct_xmit()
Date: Mon, 9 Mar 2026 17:37:59 -0700 [thread overview]
Message-ID: <d4ebcfd7-d362-40c0-9c17-629fac6ef628@gmail.com> (raw)
In-Reply-To: <2026030949-banner-rematch-db18@gregkh>
> If this is impossible to ever hit, then nothing changed here, right? So
> why is this even needed?
You're right. Would removing the default case entirely be preferred?
prev parent reply other threads:[~2026-03-10 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 0:53 [PATCH] staging: octeon: replace BUG() with WARN_ON_ONCE() in cvn_oct_xmit() Mark Adamenko
2026-03-09 16:41 ` Greg KH
2026-03-09 20:12 ` David Laight
2026-03-10 0:37 ` Mark Adamenko [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=d4ebcfd7-d362-40c0-9c17-629fac6ef628@gmail.com \
--to=marusik.adamenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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