From: Alex Elder <elder@ieee.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Alex Elder <elder@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH net-next] net: ipa: Drop unused qmi_elem_info arrays
Date: Thu, 29 Oct 2026 13:02:53 -0500 [thread overview]
Message-ID: <97e9474a-f491-4447-b128-e4a5687056ab@ieee.org> (raw)
In-Reply-To: <20261029111059.85020-2-krzysztof.kozlowski@oss.qualcomm.com>
On 10/29/26 6:11 AM, Krzysztof Kozlowski wrote:
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Did you send this before? (Why the From:?)
> 'ipa_mem_array_ei' is not used anywhere, so can be dropped completely.
> 'ipa_mem_bounds_ei' and 'ipa_mem_range_ei' are not used outside of their
> units, so they can be narrowed to file-scope.
I wonder why ipa_mem_array_ei was still defined. It must have
been used at some point... Anyway, you're right, it's not
used, so good riddance.
Did you find these by inspection?
Reviewed-by: Alex Elder <elder@riscstar.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> drivers/net/ipa/ipa_qmi_msg.c | 25 ++-----------------------
> drivers/net/ipa/ipa_qmi_msg.h | 3 ---
> 2 files changed, 2 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/net/ipa/ipa_qmi_msg.c b/drivers/net/ipa/ipa_qmi_msg.c
> index 51dc13a577a5..e2401d8475b6 100644
> --- a/drivers/net/ipa/ipa_qmi_msg.c
> +++ b/drivers/net/ipa/ipa_qmi_msg.c
> @@ -188,7 +188,7 @@ const struct qmi_elem_info ipa_init_complete_ind_ei[] = {
> };
>
> /* QMI message structure definition for struct ipa_mem_bounds */
> -const struct qmi_elem_info ipa_mem_bounds_ei[] = {
> +static const struct qmi_elem_info ipa_mem_bounds_ei[] = {
> {
> .data_type = QMI_UNSIGNED_4_BYTE,
> .elem_len = 1,
> @@ -208,29 +208,8 @@ const struct qmi_elem_info ipa_mem_bounds_ei[] = {
> },
> };
>
> -/* QMI message structure definition for struct ipa_mem_array */
> -const struct qmi_elem_info ipa_mem_array_ei[] = {
> - {
> - .data_type = QMI_UNSIGNED_4_BYTE,
> - .elem_len = 1,
> - .elem_size =
> - sizeof_field(struct ipa_mem_array, start),
> - .offset = offsetof(struct ipa_mem_array, start),
> - },
> - {
> - .data_type = QMI_UNSIGNED_4_BYTE,
> - .elem_len = 1,
> - .elem_size =
> - sizeof_field(struct ipa_mem_array, count),
> - .offset = offsetof(struct ipa_mem_array, count),
> - },
> - {
> - .data_type = QMI_EOTI,
> - },
> -};
> -
> /* QMI message structure definition for struct ipa_mem_range */
> -const struct qmi_elem_info ipa_mem_range_ei[] = {
> +static const struct qmi_elem_info ipa_mem_range_ei[] = {
> {
> .data_type = QMI_UNSIGNED_4_BYTE,
> .elem_len = 1,
> diff --git a/drivers/net/ipa/ipa_qmi_msg.h b/drivers/net/ipa/ipa_qmi_msg.h
> index 644b8c27108b..1924ac2dfa90 100644
> --- a/drivers/net/ipa/ipa_qmi_msg.h
> +++ b/drivers/net/ipa/ipa_qmi_msg.h
> @@ -253,9 +253,6 @@ extern const struct qmi_elem_info ipa_indication_register_rsp_ei[];
> extern const struct qmi_elem_info ipa_driver_init_complete_req_ei[];
> extern const struct qmi_elem_info ipa_driver_init_complete_rsp_ei[];
> extern const struct qmi_elem_info ipa_init_complete_ind_ei[];
> -extern const struct qmi_elem_info ipa_mem_bounds_ei[];
> -extern const struct qmi_elem_info ipa_mem_array_ei[];
> -extern const struct qmi_elem_info ipa_mem_range_ei[];
> extern const struct qmi_elem_info ipa_init_modem_driver_req_ei[];
> extern const struct qmi_elem_info ipa_init_modem_driver_rsp_ei[];
>
next prev parent reply other threads:[~2026-10-29 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 11:11 Krzysztof Kozlowski
2026-10-29 18:02 ` Alex Elder [this message]
2026-10-29 19:17 ` Krzysztof Kozlowski
2026-10-29 21:05 ` Alex Elder
2026-10-30 22:35 ` Jakub Kicinski
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=97e9474a-f491-4447-b128-e4a5687056ab@ieee.org \
--to=elder@ieee.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=elder@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®