From: Artur Weber <aweber.kernel@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Stanislav Jakubek <stano.jakubek@gmail.com>
Subject: Re: [PATCH v3] mfd: bcm590xx: Add support for interrupt handling
Date: Sat, 24 Jan 2026 21:23:36 +0100 [thread overview]
Message-ID: <2153fb6d-17d3-4cec-b348-894599743b93@gmail.com> (raw)
In-Reply-To: <20251023130335.GM475031@google.com>
Sorry for the late reply to a 3-month-old review, but I missed this comment:
On 23.10.2025 15:03, Lee Jones wrote:
> On Mon, 13 Oct 2025, Artur Weber wrote:
>>
>> +static bool bcm590xx_volatile_pri(struct device *dev, unsigned int reg)
>
> If I've asked a question or showed uncertainty about something, it
> usually means that changes need to be made. Asking what "pri" meant
> wasn't a one time thing. It shows that something is not clear and if
> I'm asking, others will wonder too.
>
> Can we change 'sec' to 'secondary' and 'pri' to 'primary' please?
That function was named for consistency with the other uses of "pri" and
"sec" in the code; this function is passed to a field in the struct
"bcm590xx_regmap_config_pri".
(Admittedly, "bcm590xx_regmap_volatile_pri" would be a more accurate
function name.)
I understand that the pri/sec naming could be confusing though. Should I
update the entire driver to use primary/secondary instead, or just this
one function? Or just the regmap_config?
The regmap_pri and regmap_sec names are also used in the bcm590xx struct
which is passed to other drivers (currently only the regulator driver),
changing those would also involve changing that driver, but that's fine
by me.
Best regards
Artur
next prev parent reply other threads:[~2026-01-24 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 13:41 [PATCH v3] mfd: bcm590xx: Add support for interrupt handling Artur Weber
2025-10-23 13:03 ` Lee Jones
2025-10-29 12:34 ` Artur Weber
2025-11-13 13:26 ` Lee Jones
2026-01-24 20:38 ` Artur Weber
2026-02-04 13:15 ` Lee Jones
2026-01-24 20:23 ` Artur Weber [this message]
2026-02-04 13:18 ` Lee Jones
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=2153fb6d-17d3-4cec-b348-894599743b93@gmail.com \
--to=aweber.kernel@gmail.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=stano.jakubek@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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