From: sashiko-bot@kernel.org
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: linux-s390@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Subject: Re: [PATCH v1] s390/ap: Drop unused member from ap_device_id
Date: Thu, 06 Aug 2026 16:07:13 +0000 [thread overview]
Message-ID: <20260806160713.C864D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260806155757.1281233-2-u.kleine-koenig@baylibre.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The commit message incorrectly references `device_info` instead of `driver_info`.
- [Low] The `kernel_ulong_t` typedef is no longer used after the removal of `driver_info`.
--
--- Patch [1]: [PATCH v1] s390/ap: Drop unused member from ap_device_id ---
commit 88f5caa72995cfeb3eb825fd5c1c4f333ad8e5d7
Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
s390/ap: Drop unused member from ap_device_id
This commit removes the driver_info member from the ap_device_id structure.
The structure is not part of the API/ABI and the member has no in-kernel
users.
> ap_device_id::device_info is not used in the kernel. The structure is
> also not part of API/ABI, so the unused member can just be dropped.
[Severity: Medium]
This isn't a bug in the code, but the commit message references device_info.
The struct member actually being removed by this patch is named driver_info.
> diff --git a/include/linux/device-id/ap.h b/include/linux/device-id/ap.h
> index 0992333a34db2..011af33c0bcf2 100644
> --- a/include/linux/device-id/ap.h
> +++ b/include/linux/device-id/ap.h
> @@ -14,7 +14,6 @@ typedef unsigned long kernel_ulong_t;
[Severity: Low]
Does this change leave behind an unused typedef?
With the removal of driver_info, it appears the kernel_ulong_t typedef and
its enclosing #ifdef __KERNEL__ block are no longer used anywhere in this
header file.
> struct ap_device_id {
> __u16 match_flags; /* which fields to match against */
> __u8 dev_type; /* device type */
> - kernel_ulong_t driver_info;
> };
>
> #endif /* ifndef LINUX_DEVICE_ID_AP_H */
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260806155757.1281233-2-u.kleine-koenig@baylibre.com?part=1
next prev parent reply other threads:[~2026-08-06 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 15:57 [PATCH v1] s390/ap: Drop unused member from ap_device_id Uwe Kleine-König (The Capable Hub)
2026-08-06 16:07 ` sashiko-bot [this message]
2026-08-06 16:21 ` [PATCH v2] " Uwe Kleine-König (The Capable Hub)
2026-08-06 16:31 ` sashiko-bot
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=20260806160713.C864D1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=u.kleine-koenig@baylibre.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;
as well as URLs for NNTP newsgroup(s).