From: Mark Brown <broonie@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
kernel-team@android.com, David Lechner <david@lechnology.com>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Roger Quadros <rogerq@ti.com>
Subject: Re: [RESEND PATCH v2] mfd: syscon: Use a unique name with regmap_config
Date: Fri, 28 Aug 2020 11:40:41 +0100 [thread overview]
Message-ID: <20200828104041.GA5566@sirena.org.uk> (raw)
In-Reply-To: <ef1931eb-5677-d92c-732d-b67b5263425d@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 306 bytes --]
On Thu, Aug 27, 2020 at 03:32:05PM -0500, Suman Anna wrote:
> Can you clarify the lifecycle expectations on the config->name and do you have
> any suggestions here?
The regmap name is expected to be managed by the caller and should be
live as long as the regmap is live, it is almost always static data.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-28 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 21:10 [RESEND PATCH v2] mfd: syscon: Use a unique name with regmap_config Suman Anna
2020-07-28 7:44 ` Arnd Bergmann
2020-07-28 15:34 ` Suman Anna
2020-07-28 8:01 ` Lee Jones
2020-08-27 14:46 ` Marc Zyngier
2020-08-27 18:28 ` Suman Anna
2020-08-27 20:06 ` Marc Zyngier
2020-08-27 20:32 ` Suman Anna
2020-08-28 10:40 ` Mark Brown [this message]
2020-09-03 8:26 ` Marc Zyngier
2020-09-03 13:25 ` Suman Anna
2020-09-03 16:04 ` Marc Zyngier
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=20200828104041.GA5566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=david@lechnology.com \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=kernel-team@android.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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).