From: David Woodhouse <dwmw2@infradead.org>
To: linux-mediatek@lists.infradead.org,
Frank Wunderlich <frank-w@public-files.de>,
chunkuang Hu <chunkuang.hu@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: devicetree@vger.kernel.org,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi
Date: Tue, 18 Aug 2020 08:36:55 +0100 [thread overview]
Message-ID: <5EB39D93-57C0-47AD-B0F3-09AEE643CFBF@infradead.org> (raw)
In-Reply-To: <trinity-bbc9a618-a916-40bb-b144-bffe715646a4-1597734987449@3c-app-gmx-bap75>
On 18 August 2020 08:16:27 BST, Frank Wunderlich <frank-w@public-files.de> wrote:
>Hi,
>
>i rebased changes to 5.9-rc1 [1] and include parts from Davids Series
>in my one.
>
>David: is it ok to squash your mali-commit with mine moving the other
>display-related nodes and use me as author?
Absolutely. Can the U7623 patch go along for the ride too? Was there anything else you weren't including?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-08-18 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:27 Frank Wunderlich
2020-08-07 8:27 ` [PATCH 1/2] arm: dts: mt7623: move more display-related nodes to mt7623n.dtsi Frank Wunderlich
2020-08-08 12:27 ` Aw: " Frank Wunderlich
2020-08-09 0:16 ` Chun-Kuang Hu
2020-08-09 7:21 ` Frank Wunderlich
2020-08-10 0:06 ` Chun-Kuang Hu
2020-08-10 5:39 ` Frank Wunderlich
2020-08-10 7:48 ` David Woodhouse
2020-08-10 23:28 ` Chun-Kuang Hu
2020-08-11 8:41 ` Frank Wunderlich
2020-08-11 9:35 ` David Woodhouse
2020-08-18 7:16 ` Aw: " Frank Wunderlich
2020-08-18 7:36 ` David Woodhouse [this message]
2020-08-18 7:45 ` Frank Wunderlich
2020-08-07 8:27 ` [PATCH 2/2] arm: dts: mt7623: add display subsystem related device nodes Frank Wunderlich
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=5EB39D93-57C0-47AD-B0F3-09AEE643CFBF@infradead.org \
--to=dwmw2@infradead.org \
--cc=chunkuang.hu@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.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).