lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 28 May 2021 04:24:19 +0000
From:   Wilken Gottwalt <wilken.gottwalt@...teo.net>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     Samuel Holland <samuel@...lland.org>, linux-kernel@...r.kernel.org,
        Ohad Ben-Cohen <ohad@...ery.com>,
        Baolin Wang <baolin.wang7@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Maxime Ripard <mripard@...nel.org>,
        Chen-Yu Tsai <wens@...e.org>
Subject: Re: [PATCH v7 0/2] hwspinlock: add sun6i hardware spinlock support

On Thu, 27 May 2021 22:23:09 -0500
Bjorn Andersson <bjorn.andersson@...aro.org> wrote:

> On Tue 25 May 11:07 CDT 2021, Wilken Gottwalt wrote:
> 
> > On Mon, 15 Mar 2021 23:33:31 -0500
> > Samuel Holland <samuel@...lland.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.

Oh, no, this is my fault. I just wasn't aware of that.

> 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 very much.

> Thank you,
> Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ