From: Lee Jones <lee.jones@linaro.org>
To: Baolin Wang <baolin.wang@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: Thu, 11 Jan 2018 13:08:33 +0000 [thread overview]
Message-ID: <20180111130833.gtspwn2pv6eozstk@dell> (raw)
In-Reply-To: <CAMz4kuKZjnMZYm59PBa8anfW6pcbgBh-_FDA-3ZKurLXmO6wSA@mail.gmail.com>
On Thu, 11 Jan 2018, Baolin Wang wrote:
> Hi Arnd,
>
> On 2 January 2018 at 23:36, Lee Jones <lee.jones@linaro.org> wrote:
> > Arnd,
> >
> >> 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>
> >
> > ... did you sign off on this in the end?
> >
>
> Could you apply this patch if there are no other issue? Thanks.
Arnd is the expert in this area.
Ideally I'd like his Ack before applying the patch.
--
Lee Jones
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-01-11 13:08 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 [this message]
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
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=20180111130833.gtspwn2pv6eozstk@dell \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.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
all inboxes | Powered by JetHome®