From: Greg KH <gregkh@linuxfoundation.org>
To: Minu Jin <s9430939@naver.com>
Cc: dan.carpenter@linaro.org, andy@kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: Remove wrapper functions in osdep_service
Date: Tue, 27 Jan 2026 15:44:49 +0100 [thread overview]
Message-ID: <2026012715-cottage-unsterile-00c2@gregkh> (raw)
In-Reply-To: <20260124154145.541997-1-s9430939@naver.com>
On Sun, Jan 25, 2026 at 12:41:45AM +0900, Minu Jin wrote:
> Remove unnecessary wrapper functions _rtw_malloc, _rtw_zmalloc,
> _rtw_skb_alloc, and _rtw_skb_copy from osdep_service.c.
Please do these one at a time, as doing this all at once is impossible
to review and verify.
> These wrappers were using 'in_interrupt()' to determine allocation flags,
> which is unreliable and discouraged.
>
> Callers have been updated to use standard kernel functions directly:
> - _rtw_malloc() -> kmalloc()
> - _rtw_zmalloc() -> kzalloc()
> - _rtw_skb_alloc() -> __dev_alloc_skb()
> - _rtw_skb_copy() -> skb_copy()
>
> All call sites have been manually reviewed and converted to kzalloc, kmalloc.
> The GFP flags were chosen based on the calling context:
> - GFP_ATOMIC is used for atomic contexts. (irq handler, holding
> spinlock)
> - GFP_KERNEL is used for initialization, configuration, and command paths.
How did you validate the calling contexts?
thanks,
greg k-h
prev parent reply other threads:[~2026-01-27 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 15:41 [PATCH v2] staging: rtl8723bs: Remove wrapper functions in osdep_service Minu Jin
2026-01-27 14:44 ` Greg KH [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=2026012715-cottage-unsterile-00c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andy@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=s9430939@naver.com \
/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