From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: ohad@wizery.com, linus.walleij@linaro.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Optimize the u8500_hsem hwlock driver
Date: Fri, 4 Oct 2019 21:01:39 -0700 [thread overview]
Message-ID: <20191005040139.GA5189@tuxbook-pro> (raw)
In-Reply-To: <cover.1569572448.git.baolin.wang@linaro.org>
On Fri 27 Sep 01:27 PDT 2019, Baolin Wang wrote:
> This patch set did some Optimization with changing to use devm_xxx()
> APIs to simplify the code and make code more readable.
>
Applied, with Linus' r-b
Thanks,
Bjorn
> Baolin Wang (3):
> hwspinlock: u8500_hsem: Change to use
> devm_platform_ioremap_resource()
> hwspinlock: u8500_hsem: Use devm_kzalloc() to allocate memory
> hwspinlock: u8500_hsem: Use devm_hwspin_lock_register() to register
> hwlock controller
>
> drivers/hwspinlock/u8500_hsem.c | 46 +++++++++++----------------------------
> 1 file changed, 13 insertions(+), 33 deletions(-)
>
> --
> 1.7.9.5
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-05 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 8:27 [PATCH 0/3] Optimize the u8500_hsem hwlock driver Baolin Wang
2019-09-27 8:27 ` [PATCH 1/3] hwspinlock: u8500_hsem: Change to use devm_platform_ioremap_resource() Baolin Wang
2019-10-04 21:35 ` Linus Walleij
2019-09-27 8:27 ` [PATCH 2/3] hwspinlock: u8500_hsem: Use devm_kzalloc() to allocate memory Baolin Wang
2019-10-04 21:36 ` Linus Walleij
2019-09-27 8:27 ` [PATCH 3/3] hwspinlock: u8500_hsem: Use devm_hwspin_lock_register() to register hwlock controller Baolin Wang
2019-10-04 21:38 ` Linus Walleij
2019-10-05 4:01 ` 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=20191005040139.GA5189@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=baolin.wang@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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).