From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Maulik Shah <maulik.shah@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: qcom: Remove unused macro definitions
Date: Thu, 30 Jul 2026 11:28:34 +0200 [thread overview]
Message-ID: <0b9554b5-b339-4ad3-919d-afc7fdf77d0b@oss.qualcomm.com> (raw)
In-Reply-To: <20260730-b4b4-pinctrl-unused-macros-v2-v1-1-315337a8797e@oss.qualcomm.com>
On 7/30/26 11:00 AM, Maulik Shah wrote:
> Remove macros that are defined but never used, as identified by
> -Wunused-macros:
>
> - pinctrl-qcs8300.c: QUP_I3C_{6,7,13,14}_MODE_OFFSET
> - pinctrl-sa8775p.c: QUP_I3C_{6,7,13,14}_MODE_OFFSET
> - pinctrl-sm6375.c: REG_BASE
>
> No functional impact.
>
> Assisted-by: Claude:claude-sonnet-4-6
Switch to sonnet 5!
[...]
> Signed-off-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
> ---
> Remove macros in Qualcomm pinctrl drivers that are defined but never
> used, as identified by -Wunused-macros.
>
> The QUP_I3C_*_MODE_OFFSET macros in pinctrl-qcs8300.c and
> pinctrl-sa8775p.c, and REG_BASE in pinctrl-sm6375.c have no
> references in their respective files.
>
> No functional impact.
> ---
You don't need to write a ""cover letter"" for single-patch
submissions, leaving it empty is OK. You can test that with
b4 send -d
Note that if you try to add a single-line ""cover letter"", b4
will trip on that and (likely) treat it as a series topic, which
will be unused (because there's no cover letter)..
[...]
>
> -#define QUP_I3C_6_MODE_OFFSET 0xaf000
> -#define QUP_I3C_7_MODE_OFFSET 0xb0000
> -#define QUP_I3C_13_MODE_OFFSET 0xb1000
> -#define QUP_I3C_14_MODE_OFFSET 0xb2000
Do we maybe need to use these offsets for something that we don't
support upstream yet?
Konrad
next prev parent reply other threads:[~2026-07-30 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 9:00 Maulik Shah
2026-07-30 9:28 ` Konrad Dybcio [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-29 10:43 Navya Malempati
2026-06-08 10:04 ` Konrad Dybcio
2026-06-11 12:07 ` Linus Walleij
2026-04-05 18:34 Maulik Shah
2026-04-06 0:57 ` Dmitry Baryshkov
2026-04-09 8:55 ` Linus Walleij
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=0b9554b5-b339-4ad3-919d-afc7fdf77d0b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.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®