linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] arm: dts: owl-s500: Fix incorrect PPI interrupt specifiers
Date: Thu, 27 Aug 2020 13:37:47 +0300	[thread overview]
Message-ID: <20200827103747.GC2451538@BV030612LT> (raw)
In-Reply-To: <87zh6gy53h.fsf@dell.be.48ers.dk>

On Thu, Aug 27, 2020 at 08:29:06AM +0200, Peter Korsgaard wrote:
> >>>>> "Cristian" == Cristian Ciocaltea <cristian.ciocaltea@gmail.com> writes:
> 
>  > The PPI interrupts for cortex-a9 were incorrectly specified, fix them.
>  > Fixes: fdfe7f4f9d85 ("ARM: dts: Add Actions Semi S500 and LeMaker Guitar")
>  > Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@gmail.com>
> 
> Reviewed-by: Peter Korsgaard <peter@korsgaard.com>
> 
> -- 
> Bye, Peter Korsgaard

Thanks,
Cristi

  reply	other threads:[~2020-08-27 10:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  0:00 [PATCH 0/4] Add initial support for RoseapplePi SBC Cristian Ciocaltea
2020-06-15  0:19 ` [PATCH 1/4] arm: dts: owl-s500: Fix incorrect PPI interrupt specifiers Cristian Ciocaltea
2020-08-27  6:29   ` Peter Korsgaard
2020-08-27 10:37     ` Cristian Ciocaltea [this message]
2020-06-15  0:19 ` [PATCH 2/4] dt-bindings: Add vendor prefix for RoseapplePi.org Cristian Ciocaltea
2020-07-15 18:15   ` Rob Herring
2020-06-15  0:19 ` [PATCH 3/4] dt-bindings: arm: actions: Document RoseapplePi Cristian Ciocaltea
2020-07-15 18:16   ` Rob Herring
2020-06-15  0:19 ` [PATCH 4/4] arm: dts: owl-s500: Add RoseapplePi Cristian Ciocaltea
2020-08-27  6:44   ` Peter Korsgaard
2020-08-27 14:15     ` Cristian Ciocaltea
2020-08-27 17:17       ` Peter Korsgaard

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=20200827103747.GC2451538@BV030612LT \
    --to=cristian.ciocaltea@gmail.com \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=peter@korsgaard.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;
as well as URLs for NNTP newsgroup(s).