All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nguyen Duc Thinh <ducthinh100812@gmail.com>
Cc: Luka Gejak <luka.gejak@linux.dev>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Gabriel Rondon <grondon@gmail.com>
Subject: Re: [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in enqueue()
Date: Sun, 12 Apr 2026 20:52:48 +0200	[thread overview]
Message-ID: <2026041232-kitchen-quill-add6@gregkh> (raw)
In-Reply-To: <20260412130012.5832-1-ducthinh100812@gmail.com>

On Sun, Apr 12, 2026 at 08:00:10PM +0700, Nguyen Duc Thinh wrote:
> From: Gabriel Rondon <grondon@gmail.com>
> 
> Replace BUG_ON() range check on ch_idx with a return of -EINVAL.
> 
> BUG_ON() is deprecated as it crashes the entire kernel on assertion
> failure (see Documentation/process/deprecated.rst).
> 
> Signed-off-by: Gabriel Rondon <grondon@gmail.com>
> Link: https://patch.msgid.link/20260330182255.75241-5-grondon@gmail.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

You did not sign off on this, and did I?  Where did this come from?

confused,

greg k-h

  parent reply	other threads:[~2026-04-12 18:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12 13:00 [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in enqueue() Nguyen Duc Thinh
2026-04-12 13:00 ` [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in poison_channel() Nguyen Duc Thinh
2026-04-12 13:00 ` [PATCH v3 2/2] staging: rtl8723bs: rename dot11AuthAlgrthm to fix CamelCase Nguyen Duc Thinh
2026-04-12 14:37   ` David Laight
2026-04-13  7:47   ` Dan Carpenter
2026-04-12 18:52 ` Greg KH [this message]
2026-04-12 20:43   ` [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in enqueue() Luka Gejak

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=2026041232-kitchen-quill-add6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=ducthinh100812@gmail.com \
    --cc=grondon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=luka.gejak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.