From: Luka Gejak <luka.gejak@linux.dev>
To: gregkh@linuxfoundation.org
Cc: ducthinh100812@gmail.com, grondon@gmail.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
luka.gejak@linux.dev
Subject: Re: [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in enqueue()
Date: Sun, 12 Apr 2026 22:43:21 +0200 [thread overview]
Message-ID: <03DAC8BC-B29E-4128-BBBB-D6CF541B53B6@linux.dev> (raw)
In-Reply-To: <2026041232-kitchen-quill-add6@gregkh>
>>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>
>On Sun, Apr 12, 2026 at 20:52:48 +0200, greg-hk wrote:
>You did not sign off on this, and did I? >Where did this come from?
>
>confused,
>
>greg k-h
Hi Greg,
It appears that Nguyen has sent last 2 merges patches from the
staging-next,which were there at the time of writing his commit.
Best regards,
Luka Gejak
prev parent reply other threads:[~2026-04-12 20:44 UTC|newest]
Thread overview: 6+ 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-12 18:52 ` [PATCH v3 1/2] staging: most: dim2: replace BUG_ON() in enqueue() Greg KH
2026-04-12 20:43 ` Luka Gejak [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=03DAC8BC-B29E-4128-BBBB-D6CF541B53B6@linux.dev \
--to=luka.gejak@linux.dev \
--cc=ducthinh100812@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=grondon@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