From: sashiko-bot@kernel.org
To: "Liang Haowen" <nbg2974@gmail.com>
Cc: lee@kernel.org, linux-scsi@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [RFC v7 1/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
Date: Wed, 23 Sep 2026 10:44:51 +0000 [thread overview]
Message-ID: <20260923104451.B1AC61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923103015.2365773-2-nbg2974@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] leds: undefined kzalloc_obj() macro usage
- [Low] leds: blk_rq_map_kern() missing request_queue argument
--
commit e0971e949056a90448861cfc243c852426110000
Author: Liang Haowen <nbg2974@gmail.com>
leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures
This commit introduces the ASUS Aura RGB LED driver for ROG external NVMe
enclosures. The driver manages the ENE LED controller using vendor SCSI
commands.
> --- a/drivers/leds/rgb/leds-asus-aura-scsi.c
> +++ b/drivers/leds/rgb/leds-asus-aura-scsi.c
[ ... ]
> static int ene_write(struct scsi_device *sdev, u16 reg,
> const void *data, u8 arg_count)
> {
> struct request *rq;
> struct scsi_cmnd *scmd;
> u8 cdb[ENE_CDB_LEN];
> int ret;
>
> ene_build_cdb(cdb, reg, arg_count);
>
> rq = scsi_alloc_request(sdev->request_queue, REQ_OP_DRV_OUT, 0);
> if (IS_ERR(rq))
> return PTR_ERR(rq);
>
> if (arg_count) {
> ret = blk_rq_map_kern(rq, (void *)data, arg_count, GFP_NOIO);
[Severity: Low]
Does this code omit the request_queue argument when calling
blk_rq_map_kern()? The blk_rq_map_kern() API requires five parameters,
starting with the queue pointer, but only four are passed here. This causes
a compilation error due to too few arguments.
[ ... ]
> static int asus_aura_attach(struct scsi_device *sdev)
> {
> struct asus_aura_zone *zone;
> int i, ret;
>
> if (strncmp(sdev->vendor, ARION_INQ_VENDOR, strlen(ARION_INQ_VENDOR)) ||
> strncmp(sdev->model, ARION_INQ_MODEL, strlen(ARION_INQ_MODEL)))
> return SCSI_DH_DEV_UNSUPP;
>
> zone = kzalloc_obj(*zone, GFP_KERNEL);
[Severity: Low]
Is kzalloc_obj() a valid macro or function in the kernel? Using an
undefined identifier here causes a compilation failure when allocating the
primary data structure. The standard API for this allocation would be
kzalloc().
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923103015.2365773-1-nbg2974@gmail.com?part=1
next prev parent reply other threads:[~2026-09-23 10:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 10:30 [RFC v7 0/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED driver for ROG NVMe enclosures Liang Haowen
2026-09-23 10:30 ` [RFC v7 1/1] " Liang Haowen
2026-09-23 10:44 ` sashiko-bot [this message]
2026-09-23 10:45 ` Lee Jones
2026-09-23 11:19 ` Liang Haowen
2026-09-23 10:41 ` [RFC v7 0/1] " Ilpo Järvinen
2026-09-23 12:35 ` Denis Benato
2026-09-23 12:59 ` Liang Haowen
2026-09-23 15:11 ` Marco Scardovi
2026-09-25 12:22 ` Liang Haowen
2026-09-25 12:41 ` Marco Scardovi
2026-09-25 12:45 ` Liang Haowen
-- strict thread matches above, loose matches on Subject: below --
2026-09-01 14:26 [PATCH RFC 0/1] leds: add ASUS Aura SCSI " Liang Haowen
2026-09-01 14:34 ` [PATCH RFC 1/1] " Liang Haowen
2026-09-01 14:52 ` sashiko-bot
2026-09-03 12:00 ` [PATCH RFC v2 1/1] leds: asus-aura-scsi: Add ASUS Aura RGB LED " Liang Haowen
2026-09-03 12:24 ` sashiko-bot
2026-09-03 16:13 ` Lee Jones
2026-09-04 12:30 ` [PATCH RFC v3 0/1] " Liang Haowen
2026-09-04 12:30 ` [PATCH RFC v3 1/1] " Liang Haowen
2026-09-04 13:15 ` sashiko-bot
2026-09-10 9:32 ` Lee Jones
2026-09-15 12:48 ` [PATCH RFC v4 0/1] " Liang Haowen
2026-09-15 12:49 ` [PATCH RFC v4 1/1] " Liang Haowen
2026-09-15 13:00 ` sashiko-bot
2026-09-16 10:43 ` Lee Jones
2026-09-16 12:15 ` [PATCH RFC v5 0/1] " Liang Haowen
2026-09-16 12:15 ` [PATCH RFC v5 1/1] " Liang Haowen
2026-09-16 12:27 ` sashiko-bot
2026-09-16 13:06 ` Lee Jones
2026-09-16 14:22 ` [PATCH RFC v6 0/1] " Liang Haowen
2026-09-16 14:22 ` [PATCH RFC v6 1/1] " Liang Haowen
2026-09-16 14:38 ` sashiko-bot
2026-09-17 11:28 ` Lee Jones
2026-09-17 11:49 ` Liang Haowen
2026-09-23 9:45 ` Lee Jones
2026-09-23 10:18 ` Liang Haowen
[not found] ` <20260923102812.2353292-1-nbg2974@gmail.com>
2026-09-23 10:12 ` Ilpo Järvinen
2026-09-16 14:23 ` [PATCH RFC v5 " Liang Haowen
2026-09-16 12:15 ` [PATCH RFC v4 " Liang Haowen
2026-09-15 12:49 ` [PATCH RFC v3 " Liang Haowen
2026-09-04 12:45 ` [PATCH RFC v2 " Liang Haowen
2026-09-03 12:00 ` [PATCH RFC v2 0/1] " Liang Haowen
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=20260923104451.B1AC61F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nbg2974@gmail.com \
--cc=sashiko-reviews@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