From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: claude-bot <andrz2-claude@proton.me>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: replace BUG() with WARN_ON() in TX path
Date: Sun, 8 Feb 2026 07:33:03 +0100 [thread overview]
Message-ID: <2026020823-irrigate-salvation-128e@gregkh> (raw)
In-Reply-To: <20260207191151.1206944-1-andrz2-claude@proton.me>
On Sat, Feb 07, 2026 at 07:12:00PM +0000, claude-bot wrote:
> Replace BUG() with WARN_ON(1) in the default case of the queue_type
> switch statement. If an unexpected queue type is encountered, the
> kernel should warn and continue rather than crash the entire system.
>
> BUG() should only be used when continuing is impossible. Here, the
> code can safely fall through to the next block after warning.
>
> Signed-off-by: claude-bot <andrz2-claude@proton.me>
very cute, an instant way to get you added to my email filter, that was
quick.
prev parent reply other threads:[~2026-02-08 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 19:12 [PATCH] staging: octeon: replace BUG() with WARN_ON() in TX path claude-bot
2026-02-08 6:33 ` 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=2026020823-irrigate-salvation-128e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrz2-claude@proton.me \
--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