Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 27 May 2021 22:23:09 -0500
From:   Bjorn Andersson <bjorn.andersson@linaro.org>
To:     Wilken Gottwalt <wilken.gottwalt@posteo.net>
Cc:     Samuel Holland <samuel@sholland.org>, linux-kernel@vger.kernel.org,
        Ohad Ben-Cohen <ohad@wizery.com>,
        Baolin Wang <baolin.wang7@gmail.com>,
        Rob Herring <robh+dt@kernel.org>,
        Maxime Ripard <mripard@kernel.org>,
        Chen-Yu Tsai <wens@csie.org>,
        Jernej Skrabec <jernej.skrabec@siol.net>
Subject: Re: [PATCH v7 0/2] hwspinlock: add sun6i hardware spinlock support
Message-ID: <YLBiHQaW6H4K7QyO@builder.lan>
References: <cover.1615713499.git.wilken.gottwalt@posteo.net>
 <95e93676-cfcf-1aed-1741-d69b72286033@sholland.org>
 <20210525180744.24187bb1@monster.powergraphx.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210525180744.24187bb1@monster.powergraphx.local>
Precedence: bulk

On Tue 25 May 11:07 CDT 2021, Wilken Gottwalt wrote:

> On Mon, 15 Mar 2021 23:33:31 -0500
> Samuel Holland <samuel@sholland.org> wrote:
> 
> > On 3/14/21 4:30 AM, Wilken Gottwalt wrote:
> > > Wilken Gottwalt (2):
> > >   dt-bindings: hwlock: add sun6i_hwspinlock
> > >   hwspinlock: add sun6i hardware spinlock support
> > > 
> > >  .../allwinner,sun6i-a31-hwspinlock.yaml       |  45 ++++
> > >  MAINTAINERS                                   |   6 +
> > >  drivers/hwspinlock/Kconfig                    |   9 +
> > >  drivers/hwspinlock/Makefile                   |   1 +
> > >  drivers/hwspinlock/sun6i_hwspinlock.c         | 210 ++++++++++++++++++
> > >  5 files changed, 271 insertions(+)
> > >  create mode 100644 Documentation/devicetree/bindings/hwlock/allwinner,sun6i-a31-hwspinlock.yaml
> > >  create mode 100644 drivers/hwspinlock/sun6i_hwspinlock.c
> > > 
> > 
> > Thanks for the very thorough testing!
> 
> So when will this end up in mainstream? Or do I have to somehing to get this
> triggered? This is not my first driver and back then it was included into
> mainline without anything special on my side. I'm a bit confused. Did I miss
> something?
> 

Sorry, I wasn't paying enough attention and you didn't Cc
linux-remoteproc@ (as described in MAINTAINERS) so I lost track of the
patch.

It's now been applied, I'll do some build testing on the way out but it
should show up in linux-next in the coming days.

Thank you,
Bjorn