devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Andre Przywara <andre.przywara@arm.com>
Cc: soc@kernel.org, Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, Wei Xu <xuwei5@hisilicon.com>,
	Chanho Min <chanho.min@lge.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] ARM/arm64: dts: Fix SP804/SP805 users
Date: Sat, 3 Oct 2020 12:57:27 -0700	[thread overview]
Message-ID: <20201003195727.GH8203@lx2k> (raw)
In-Reply-To: <20200907121831.242281-1-andre.przywara@arm.com>

On Mon, Sep 07, 2020 at 01:18:25PM +0100, Andre Przywara wrote:
> Those are the remaining patches of the SP804/SP805 DT fixes. [1][2]
> ARM, Broadcom and Freescale have their respective fixes queued through
> their maintainers already, but I haven't heard back from LG or HiSilicon
> so far.
> So can those patches be taken through armsoc directly?

I've applied the ones who didn't have replies from platform maintainers yet.

Thanks!


-Olof

      parent reply	other threads:[~2020-10-03 20:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07 12:18 [PATCH v3 0/6] ARM/arm64: dts: Fix SP804/SP805 users Andre Przywara
2020-09-07 12:18 ` [PATCH v3 1/6] ARM: dts: hisilicon: Fix SP804 users Andre Przywara
2020-09-16  1:44   ` Wei Xu
2020-09-07 12:18 ` [PATCH v3 2/6] ARM: dts: nspire: " Andre Przywara
2020-09-07 12:18 ` [PATCH v3 3/6] arm64: dts: lg: " Andre Przywara
2020-09-07 12:18 ` [PATCH v3 4/6] arm64: dts: hisilicon: Fix SP805 clocks Andre Przywara
2020-09-16  1:45   ` Wei Xu
2020-09-07 12:18 ` [PATCH v3 5/6] arm64: dts: lg: " Andre Przywara
2020-09-07 12:18 ` [PATCH v3 6/6] ARM: dts: hisilicon: " Andre Przywara
2020-09-16  1:42   ` Wei Xu
2020-10-03 19:57 ` Olof Johansson [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=20201003195727.GH8203@lx2k \
    --to=olof@lixom.net \
    --cc=andre.przywara@arm.com \
    --cc=chanho.min@lge.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=soc@kernel.org \
    --cc=xuwei5@hisilicon.com \
    /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).