From: David Miller <davem@davemloft.net>
To: icenowy@aosc.io
Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
andrew@lunn.ch, f.fainelli@gmail.com, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mripard@kernel.org, linux-sunxi@googlegroups.com,
robh+dt@kernel.org, wens@csie.org, hkallweit1@gmail.com
Subject: Re: [PATCH 0/3] Pine64+ specific hacks for RTL8211E Ethernet PHY
Date: Tue, 01 Oct 2019 09:41:44 -0700 (PDT) [thread overview]
Message-ID: <20191001.094144.1520493336302505890.davem@davemloft.net> (raw)
In-Reply-To: <D1124458-D5CB-4AFF-B106-C6EA1A98100F@aosc.io>
From: Icenowy Zheng <icenowy@aosc.io>
Date: Wed, 02 Oct 2019 00:31:25 +0800
> I have tried to ask via TL Lim from Pine64, because I have no way
> to communicate directly to Realtek. However TL cannot get anything
> more from Realtek.
We have several Realtek developers who post here as part of maintaining
the upstream copy of their drivers, and upstream developers of other
Realtek parts who sometimes interact with Realtek.
Be creative and work with these people to try to get to the right
people.
Please stop making excuses and do the right thing.
Thank you.
next prev parent reply other threads:[~2019-10-01 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 8:29 [PATCH 0/3] Pine64+ specific hacks for RTL8211E Ethernet PHY Icenowy Zheng
2019-10-01 8:29 ` [PATCH 1/3] dt-bindings: add binding " Icenowy Zheng
2019-10-01 8:29 ` [PATCH 2/3] net: phy: realtek: add config hack for broken RTL8211E on Pine64+ boards Icenowy Zheng
2019-10-01 8:29 ` [PATCH 3/3] arm64: allwinner: a64: dts: apply hack for RTL8211E on Pine64+ Icenowy Zheng
2019-10-01 16:06 ` [PATCH 0/3] Pine64+ specific hacks for RTL8211E Ethernet PHY David Miller
2019-10-01 16:08 ` Icenowy Zheng
2019-10-01 16:30 ` David Miller
2019-10-01 16:31 ` Icenowy Zheng
2019-10-01 16:41 ` David Miller [this message]
2019-10-01 16:47 ` Florian Fainelli
2019-10-01 16:52 ` Andrew Lunn
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=20191001.094144.1520493336302505890.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).