From: Chuanjia Liu <chuanjia.liu@mediatek.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
jianjun.wang@mediatek.com, Ryder Lee <ryder.lee@mediatek.com>,
linux-mediatek@lists.infradead.org, yong.wu@mediatek.com
Subject: Re: Aw: Re: [PATCH v4 0/4] Split PCIe node to comply with hardware design
Date: Thu, 10 Sep 2020 15:02:52 +0800 [thread overview]
Message-ID: <1599721372.7466.15.camel@mhfsdcap03> (raw)
In-Reply-To: <trinity-74abdbb2-2ddc-440a-85c8-97e80e9eb2ed-1599545604475@3c-app-gmx-bs38>
On Tue, 2020-09-08 at 08:13 +0200, Frank Wunderlich wrote:
> Hi,
>
> i don't see this Patchset in 5.9-rc4
>
> is anything missing?
>
> regards Frank
Thanks for ping this mail,
<vger.kernel.org> mali list consider this patchset is SPAM
because of my environmental problems.
I have fixed this problem and send the V5 version.
It can be seen correctly in linux-pci mail list.
Now I guess the maintainer will help review and apply this.
regards Chuanjia
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-09-10 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 7:49 [PATCH v4 0/4] Split PCIe node to comply with hardware design chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 1/4] dt-bindings: pci: mediatek: Modified the Device tree bindings chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 2/4] PCI: mediatek: Use regmap to get shared pcie-cfg base chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 3/4] arm64: dts: mediatek: Split PCIe node for MT2712 and MT7622 chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 4/4] ARM: dts: mediatek: Modified MT7629 PCIe node chuanjia.liu
2020-08-03 7:46 ` [PATCH v4 0/4] Split PCIe node to comply with hardware design Chuanjia Liu
2020-09-08 6:13 ` Aw: " Frank Wunderlich
2020-09-10 7:02 ` Chuanjia Liu [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=1599721372.7466.15.camel@mhfsdcap03 \
--to=chuanjia.liu@mediatek.com \
--cc=frank-w@public-files.de \
--cc=jianjun.wang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=yong.wu@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