From: Ohad Ben-Cohen <ohad@wizery.com> To: Stephen Boyd <sboyd@codeaurora.org>, Linus Walleij <linus.walleij@linaro.org> Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "Russell King" <linux@arm.linux.org.uk>, "Fernando Guzman Lugo" <fernando.lugo@ti.com>, "Sjur Brændeland" <sjur.brandeland@stericsson.com> Subject: Re: [PATCH] remoteproc: adopt the driver core's alloc/add/del/put naming Date: Sun, 15 Jul 2012 13:14:44 +0300 [thread overview] Message-ID: <CAK=WgbbO72S9=T-dnJBHE5d5k9H8dtYFtxe_AMSe+ut+0ZPOHg@mail.gmail.com> (raw) In-Reply-To: <4FF50107.8030406@codeaurora.org> On Thu, Jul 5, 2012 at 5:50 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > On 7/4/2012 6:36 AM, Ohad Ben-Cohen wrote: >> To make remoteproc's API more intuitive for developers, we adopt >> the driver core's naming, i.e. alloc -> add -> del -> put. We'll also >> add register/unregister when their first user shows up. >> >> Otherwise - there's no functional change here. >> >> Suggested by Russell King <linux@arm.linux.org.uk>. >> >> Cc: Russell King <linux@arm.linux.org.uk> > > Acked-by: Stephen Boyd <sboyd@codeaurora.org> On Thu, Jul 5, 2012 at 2:50 AM, Linus Walleij <linus.walleij@linaro.org> wrote: > I understand this patch and it's a good thing, so: > Reviewed-by: Linus Walleij <linus.walleij@linaro.org> > > Yours, > Linus Walleij Thanks Linus and Stephen. Applied.
WARNING: multiple messages have this Message-ID (diff)
From: ohad@wizery.com (Ohad Ben-Cohen) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] remoteproc: adopt the driver core's alloc/add/del/put naming Date: Sun, 15 Jul 2012 13:14:44 +0300 [thread overview] Message-ID: <CAK=WgbbO72S9=T-dnJBHE5d5k9H8dtYFtxe_AMSe+ut+0ZPOHg@mail.gmail.com> (raw) In-Reply-To: <4FF50107.8030406@codeaurora.org> On Thu, Jul 5, 2012 at 5:50 AM, Stephen Boyd <sboyd@codeaurora.org> wrote: > On 7/4/2012 6:36 AM, Ohad Ben-Cohen wrote: >> To make remoteproc's API more intuitive for developers, we adopt >> the driver core's naming, i.e. alloc -> add -> del -> put. We'll also >> add register/unregister when their first user shows up. >> >> Otherwise - there's no functional change here. >> >> Suggested by Russell King <linux@arm.linux.org.uk>. >> >> Cc: Russell King <linux@arm.linux.org.uk> > > Acked-by: Stephen Boyd <sboyd@codeaurora.org> On Thu, Jul 5, 2012 at 2:50 AM, Linus Walleij <linus.walleij@linaro.org> wrote: > I understand this patch and it's a good thing, so: > Reviewed-by: Linus Walleij <linus.walleij@linaro.org> > > Yours, > Linus Walleij Thanks Linus and Stephen. Applied.
next prev parent reply other threads:[~2012-07-15 10:15 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-04 13:36 [PATCH] remoteproc: adopt the driver core's alloc/add/del/put naming Ohad Ben-Cohen 2012-07-04 13:36 ` Ohad Ben-Cohen 2012-07-04 13:36 ` Ohad Ben-Cohen 2012-07-04 23:50 ` Linus Walleij 2012-07-04 23:50 ` Linus Walleij 2012-07-04 23:50 ` Linus Walleij 2012-07-05 2:50 ` Stephen Boyd 2012-07-05 2:50 ` Stephen Boyd 2012-07-05 2:50 ` Stephen Boyd 2012-07-15 10:14 ` Ohad Ben-Cohen [this message] 2012-07-15 10:14 ` Ohad Ben-Cohen
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='CAK=WgbbO72S9=T-dnJBHE5d5k9H8dtYFtxe_AMSe+ut+0ZPOHg@mail.gmail.com' \ --to=ohad@wizery.com \ --cc=fernando.lugo@ti.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=sboyd@codeaurora.org \ --cc=sjur.brandeland@stericsson.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.