[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200930120849.GG4974@sirena.org.uk>
Date: Wed, 30 Sep 2020 13:08:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
rafael@...nel.org, lgirdwood@...il.com, perex@...ex.cz,
tiwai@...e.com, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, srivasam@...eaurora.org,
rohitkr@...eaurora.org
Subject: Re: [PATCH v2 1/2] regmap: add support to
regmap_field_bulk_alloc/free apis
On Wed, Sep 30, 2020 at 01:59:15PM +0200, Greg KH wrote:
> On Fri, Sep 25, 2020 at 05:48:55PM +0100, Srinivas Kandagatla wrote:
> > +int devm_regmap_field_bulk_alloc(struct device *dev, struct regmap *regmap,
> > + struct regmap_field **field,
> > + struct reg_field *reg_field, int num_fields);
> > +void devm_regmap_field_bulk_free(struct device *dev,
> > + struct regmap_field *field);
> > +
>
> You only have a patch that uses these last two functions, so why add all
> 4? We don't add infrastructure to the kernel without users.
We have managed versions of the other regmap allocation functions, it
makes sense for consistency to have managed versions of these too. I
think there's a meaningful difference between a simple and expected
wrapper like these and infrastructure which hasn't been proved out by
users.
Please delete unneeded context from mails when replying. Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists