From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Georgi Djakov <djakov@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] interconnect: qcom: Constify struct qcom_icc_qosbox
Date: Mon, 17 Aug 2026 09:58:26 +0200 [thread overview]
Message-ID: <720083ed-a149-4872-98d5-c4157586d628@oss.qualcomm.com> (raw)
In-Reply-To: <f9d9ab49e961b3bf3f9bad39f22cf8b06afb2381.1786554463.git.christophe.jaillet@wanadoo.fr>
On 8/12/26 7:08 PM, Christophe JAILLET wrote:
> 'struct qcom_icc_qosbox' are not modified in these drivers.
>
> Constifying these structures moves some data to a read-only section, so
> increases overall security.
>
> On a x86_64, with allmodconfig:
> Before:
> ======
> text data bss dec hex filename
> 7807 18632 0 26439 6747 drivers/interconnect/qcom/eliza.o
> 10027 20176 0 30203 75fb drivers/interconnect/qcom/milos.o
> 8768 22640 0 31408 7ab0 drivers/interconnect/qcom/sm6350.o
> 7626 22000 0 29626 73ba drivers/interconnect/qcom/sm8650.o
>
> After:
> =====
> text data bss dec hex filename
> 8095 18344 0 26439 6747 drivers/interconnect/qcom/eliza.o
> 11079 19120 0 30199 75f7 drivers/interconnect/qcom/milos.o
> 9668 21744 0 31412 7ab4 drivers/interconnect/qcom/sm6350.o
> 8746 20880 0 29626 73ba drivers/interconnect/qcom/sm8650.o
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
Thanks!
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2026-08-17 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:08 Christophe JAILLET
2026-08-12 18:46 ` Dmitry Baryshkov
2026-08-17 7:58 ` Konrad Dybcio [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=720083ed-a149-4872-98d5-c4157586d628@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=djakov@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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®