linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: fuyao@allwinnertech.com
Cc: wens@csie.org, linux-remoteproc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] introduce sunxi hwspinlock
Date: Fri, 20 Nov 2020 17:07:10 +0100	[thread overview]
Message-ID: <20201120160710.wlkl5cdfqlrym2fj@gilmour> (raw)
In-Reply-To: <cover.1605767679.git.fuyao@allwinnertech.com>

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

Hi!

On Thu, Nov 19, 2020 at 02:44:51PM +0800, fuyao@allwinnertech.com wrote:
> From: fuyao <fuyao@allwinnertech.com>
> 
> this series add hwspinlock of sunxi. it provides hardware assistance for
> synchronization between the multiple processors in the system.
> (Or1k, Cortex-A7, Cortex-A53, Xtensa)

Xtensa? Which SoC has an Xtensa core?

Unfortunately, there's been a submission of the same driver earlier this week:
https://lore.kernel.org/lkml/cover.1605693132.git.wilken.gottwalt@posteo.net/

It would be great if you could point out whatever issue there is with
that patch series (it looks like the retry delay could be useful for
example).

Thanks!
Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2020-11-20 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  6:44 [PATCH 0/2] introduce sunxi hwspinlock fuyao
2020-11-19  6:44 ` [PATCH 1/2] dt-bindings: hwlock: add sunxi hwlock fuyao
2020-11-19  6:44 ` [PATCH 2/2] hwspinlock: add SUNXI implementation fuyao
2020-11-21  4:01   ` Bjorn Andersson
2020-11-21 14:33     ` fuyao
2020-11-20 16:07 ` Maxime Ripard [this message]
2020-11-21 14:08   ` [PATCH 0/2] introduce sunxi hwspinlock fuyao

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=20201120160710.wlkl5cdfqlrym2fj@gilmour \
    --to=maxime@cerno.tech \
    --cc=fuyao@allwinnertech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).