From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Newton Subject: Re: [RFC 2/8] remoteproc: add omap implementation Date: Wed, 22 Jun 2011 11:05:41 +0100 Message-ID: References: <1308640714-17961-1-git-send-email-ohad@wizery.com> <1308640714-17961-3-git-send-email-ohad@wizery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <1308640714-17961-3-git-send-email-ohad@wizery.com> Sender: linux-kernel-owner@vger.kernel.org To: Ohad Ben-Cohen Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, akpm@linux-foundation.org, Brian Swetland , Arnd Bergmann , Grant Likely , davinci-linux-open-source , Rusty Russell , "Guzman Lugo, Fernando" List-Id: linux-omap@vger.kernel.org On Tue, Jun 21, 2011 at 8:18 AM, Ohad Ben-Cohen wrote= : > +/* bootaddr isn't needed for the dual M3's */ > +static inline int omap_rproc_start(struct rproc *rproc, u64 bootaddr= ) > +static inline int omap_rproc_stop(struct rproc *rproc) These two functions don't need to be inline as far as I can see. > +static struct rproc_ops omap_rproc_ops =3D { > + =A0 =A0 =A0 .start =3D omap_rproc_start, > + =A0 =A0 =A0 .stop =3D omap_rproc_stop, > +};