From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Baolin Wang <baolin.wang7@gmail.com>
Cc: ohad@wizery.com, linux-omap@vger.kernel.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/3] Some improvements for OMAP hwspinlock
Date: Tue, 21 Jan 2020 16:15:57 -0800 [thread overview]
Message-ID: <20200122001557.GC14744@builder> (raw)
In-Reply-To: <cover.1578453062.git.baolin.wang7@gmail.com>
On Tue 07 Jan 19:13 PST 2020, Baolin Wang wrote:
> This patch set did some optimization for OMAP hwlock controller with
> changing to use some devm_xxx APIs to simplify code.
>
Applied the first 2 patches, thanks.
> Baolin Wang (3):
> hwspinlock: omap: Change to use devm_platform_ioremap_resource()
> hwspinlock: omap: Use devm_kzalloc() to allocate memory
> hwspinlock: omap: Use devm_hwspin_lock_register() to register hwlock
> controller
>
> drivers/hwspinlock/omap_hwspinlock.c | 45 ++++++++++------------------------
> 1 file changed, 13 insertions(+), 32 deletions(-)
>
> --
> 1.7.9.5
>
prev parent reply other threads:[~2020-01-22 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 3:13 [PATCH RESEND 0/3] Some improvements for OMAP hwspinlock Baolin Wang
2020-01-08 3:13 ` [PATCH RESEND 1/3] hwspinlock: omap: Change to use devm_platform_ioremap_resource() Baolin Wang
2020-01-08 3:14 ` [PATCH RESEND 2/3] hwspinlock: omap: Use devm_kzalloc() to allocate memory Baolin Wang
2020-01-08 3:14 ` [PATCH RESEND 3/3] hwspinlock: omap: Use devm_hwspin_lock_register() to register hwlock controller Baolin Wang
2020-01-22 0:15 ` Bjorn Andersson
2020-01-25 4:10 ` Baolin Wang
2020-01-22 0:15 ` Bjorn Andersson [this message]
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=20200122001557.GC14744@builder \
--to=bjorn.andersson@linaro.org \
--cc=baolin.wang7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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).