From: "Andreas Färber" <afaerber@suse.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-realtek-soc@lists.infradead.org,
LAKML <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Mark Rutland <mark.rutland@arm.com>,
Heiko Stuebner <heiko@sntech.de>,
Neil Armstrong <narmstrong@baylibre.com>,
Maxime Ripard <mripard@kernel.org>,
Guillaume Gardet <guillaume.gardet@arm.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: gpu: mali-midgard: Tidy up conversion to YAML
Date: Thu, 7 Nov 2019 11:03:26 +0100 [thread overview]
Message-ID: <3c9d7a8c-94e4-60b9-9a84-f368e227666e@suse.de> (raw)
In-Reply-To: <CAL_JsqLDFefWVdiPuAktctuBpBeOvG-OVhX2aZn=UaiN55nodg@mail.gmail.com>
Am 06.11.19 um 16:34 schrieb Rob Herring:
> On Wed, Nov 6, 2019 at 9:07 AM Andreas Färber <afaerber@suse.de> wrote:
>> Am Mittwoch, den 06.11.2019, 08:24 -0600 schrieb Rob Herring:
>>> This patch is problematic because there's changes in arm-soc juno/dt
>>> branch and there's now a patch for exynos5420 (t628). I'd propose I
>>> apply this such that we don't get a merge conflict with juno/dt and
>>> we
>>> finish resorting after rc1 (or when both branches are in Linus'
>>> tree).
>>
>> This series has dependencies for the Realtek-side RFC patches and is
>> not yet ready to merge, so you can take this prep PATCH through your
>> tree for v5.6 probably, or feel free to rebase/rework as you see fit -
>> I'd just appreciate being credited at least via Reported-by. :)
>
> I was assuming the non-RFC patches are good to go, so I was going to
> pick up 1, 2, and 7.
Actually 1, 2 and 4 should be good to go; 7 if you fix the subject or if
I respin. Also 6 if you can have someone check that no new properties
will be needed for 470 (no Linux driver support yet).
All but 1 assuming you'll be okay to add SoC-specific restrictions on
clocks/resets/domains later, once we've fully figured it out (cf. cover
letter for current errors - looking into power domains next).
Regards,
Andreas
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
next prev parent reply other threads:[~2019-11-07 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:39 [RFC 0/7] ARM: dts: Mali for Realtek RTD1195/RTD1295 Andreas Färber
2019-11-04 1:39 ` [PATCH 1/7] dt-bindings: gpu: mali-midgard: Tidy up conversion to YAML Andreas Färber
2019-11-06 14:24 ` Rob Herring
2019-11-06 14:36 ` Krzysztof Kozlowski
2019-11-06 15:07 ` Andreas Färber
2019-11-06 15:34 ` Rob Herring
2019-11-07 10:03 ` Andreas Färber [this message]
2019-11-04 1:39 ` [PATCH 2/7] dt-bindings: gpu: mali-midgard: Add Realtek RTD1295 Andreas Färber
2019-11-13 3:21 ` Rob Herring
2019-11-04 1:39 ` [RFC 3/7] arm64: dts: realtek: rtd1295: Add Mali node Andreas Färber
2019-11-04 1:39 ` [RFC 4/7] dt-bindings: gpu: mali-utgard: Add Realtek RTD1195 Andreas Färber
2019-11-04 1:39 ` [RFC 5/7] ARM: dts: rtd1195: Add Mali node Andreas Färber
2019-11-04 1:39 ` [RFC 6/7] dt-bindings: gpu: mali-utgard: Add Realtek RTD1395 Andreas Färber
2019-11-04 1:39 ` [PATCH 7/7] dt-bindings: gpu: arm-bifrost: Add Realtek RTD1619 Andreas Färber
2019-11-04 1:49 ` Andreas Färber
2019-11-13 3:21 ` Rob Herring
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=3c9d7a8c-94e4-60b9-9a84-f368e227666e@suse.de \
--to=afaerber@suse.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guillaume.gardet@arm.com \
--cc=heiko@sntech.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh@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).