[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJaT-Y7DHQS5ZZ0TP6r0iPDbUZwU-Kec5MSE7DOPgZxCg@mail.gmail.com>
Date: Fri, 9 Jan 2015 11:53:01 -0600
From: Rob Herring <robherring2@...il.com>
To: "George G. Davis" <ggdavisiv@...il.com>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
"George G. Davis" <george_davis@...tor.com>
Subject: Re: [PATCH] drivers: of: Export of_reserved_mem_device_{init,release}
On Fri, Jan 9, 2015 at 8:29 AM, George G. Davis <ggdavisiv@...il.com> wrote:
> Export of_reserved_mem_device_{init,release} so that modules
> can initialize and release their assigned per-device cma_area.
I believe the original intent was for the core bus code to call these
functions. While the commit adding them says "automated assignment"
that part did not go in. As it stands, there are no in tree users of
these functions.
Marek, comments?
Rob
>
> Signed-off-by: George G. Davis <george_davis@...tor.com>
> ---
> drivers/of/of_reserved_mem.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/of/of_reserved_mem.c b/drivers/of/of_reserved_mem.c
> index dc566b3..5eeb5b2 100644
> --- a/drivers/of/of_reserved_mem.c
> +++ b/drivers/of/of_reserved_mem.c
> @@ -265,6 +265,7 @@ int of_reserved_mem_device_init(struct device *dev)
>
> return ret;
> }
> +EXPORT_SYMBOL(of_reserved_mem_device_init);
>
> /**
> * of_reserved_mem_device_release() - release reserved memory device structures
> @@ -289,3 +290,4 @@ void of_reserved_mem_device_release(struct device *dev)
>
> rmem->ops->device_release(rmem, dev);
> }
> +EXPORT_SYMBOL(of_reserved_mem_device_release);
> --
> 1.9.3
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists