linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mark Brown <broonie@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	DTML <devicetree@vger.kernel.org>
Subject: Re: [PATCH v7 2/2] mfd: syscon: Add hardware spinlock support
Date: Tue, 23 Jan 2018 16:05:15 +0800	[thread overview]
Message-ID: <CAMz4kuK9mng38+fVVCjta1uOJgG_fKtf29NWiUXW_hY55guTjQ@mail.gmail.com> (raw)
In-Reply-To: <20180122134336.e7phrckbpwvxwsfz@dell>

Hi Lee,

On 22 January 2018 at 21:43, Lee Jones <lee.jones@linaro.org> wrote:
> On Thu, 11 Jan 2018, Lee Jones wrote:
>> On Mon, 25 Dec 2017, Baolin Wang wrote:
>>
>> > Some system control registers need hardware spinlock to synchronize
>> > between the multiple subsystems, so we should add hardware spinlock
>> > support for syscon.
>> >
>> > Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
>> > Acked-by: Rob Herring <robh@kernel.org>
>> > ---
>> > Changes since v6:
>> >  - Treat hwlock id 0 as valid for regmap.
>> >
>> > Changes since v5:
>> >  - Fix the case that hwspinlock is not enabled.
>> >
>> > Changes since v4:
>> >  - Add one exapmle to show how to add hwlock.
>> >  - Fix the coding style issue.
>> >
>> > Changes since v3:
>> >  - Add error handling for of_hwspin_lock_get_id()
>> >
>> > Changes since v2:
>> >  - Add acked tag from Rob.
>> >
>> > Changes since v1:
>> >  - Remove timeout configuration.
>> >  - Modify the binding file to add hwlocks.
>> > ---
>> >  Documentation/devicetree/bindings/mfd/syscon.txt |    8 ++++++++
>> >  drivers/mfd/syscon.c                             |   19 +++++++++++++++++++
>> >  2 files changed, 27 insertions(+)
>>
>> Applied, thanks.
>
> In order to avoid confusion, I should like to tell you that this patch
> is applied for v4.17, not v4.16.

This patch has been applied into Mark's branch[1] with your ACK, so
Mark should drop this patch from his branch and you will pick it and
merge it into v4.17?

[1] https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=topic/hwspinlock&id=3bafc09e779710abaa7b836fe3bbeeeab7754c2b

-- 
Baolin.wang
Best Regards

  reply	other threads:[~2018-01-23  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25  6:37 [PATCH v7 1/2] regmap: Add one flag to indicate if a hwlock should be used Baolin Wang
2017-12-25  6:37 ` [PATCH v7 2/2] mfd: syscon: Add hardware spinlock support Baolin Wang
2018-01-02 15:36   ` Lee Jones
2018-01-11 12:36     ` Baolin Wang
2018-01-11 13:08       ` Lee Jones
2018-01-11 14:27         ` Arnd Bergmann
2018-01-11 15:22   ` Lee Jones
2018-01-22 13:43     ` Lee Jones
2018-01-23  8:05       ` Baolin Wang [this message]
2018-01-23  9:11         ` Lee Jones
2018-01-12 20:01   ` Applied "mfd: syscon: Add hardware spinlock support" to the regmap tree Mark Brown
2017-12-27 10:39 ` Applied "regmap: Add one flag to indicate if a hwlock should be used" " Mark Brown

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=CAMz4kuK9mng38+fVVCjta1uOJgG_fKtf29NWiUXW_hY55guTjQ@mail.gmail.com \
    --to=baolin.wang@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    /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).