mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wilken Gottwalt <wilken.gottwalt@posteo.net>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
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>
Subject: Re: [PATCH v7 0/2] hwspinlock: add sun6i hardware spinlock support
Date: Fri, 28 May 2021 04:24:19 +0000	[thread overview]
Message-ID: <20210528062419.15d5189d@monster.powergraphx.local> (raw)
In-Reply-To: <YLBiHQaW6H4K7QyO@builder.lan>

On Thu, 27 May 2021 22:23:09 -0500
Bjorn Andersson <bjorn.andersson@linaro.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@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.

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


      reply	other threads:[~2021-05-28  4:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14  9:30 Wilken Gottwalt
2021-03-14  9:30 ` [PATCH v7 1/2] dt-bindings: hwlock: add sun6i_hwspinlock Wilken Gottwalt
2021-03-15 16:09   ` Maxime Ripard
2021-06-01 22:12   ` Rob Herring
2021-06-03  4:59     ` Wilken Gottwalt
2021-03-14  9:31 ` [PATCH v7 2/2] hwspinlock: add sun6i hardware spinlock support Wilken Gottwalt
2021-03-15 16:12   ` Maxime Ripard
2021-03-18 14:06     ` Wilken Gottwalt
2021-03-16  4:33 ` [PATCH v7 0/2] " Samuel Holland
2021-05-25 16:07   ` Wilken Gottwalt
2021-05-26 18:58     ` Maxime Ripard
2021-05-28  3:23     ` Bjorn Andersson
2021-05-28  4:24       ` Wilken Gottwalt [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=20210528062419.15d5189d@monster.powergraphx.local \
    --to=wilken.gottwalt@posteo.net \
    --cc=baolin.wang7@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=ohad@wizery.com \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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

Powered by JetHome