Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8571870ybn; Tue, 1 Oct 2019 10:00:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqy3f9BfvQ37JdzAlC6QJtXyNgTg5wgQOIaFHNRCpqwEY5f7azZ7brEnvOX/brYPUPYWFLYM X-Received: by 2002:aa7:dcd7:: with SMTP id w23mr26235448edu.170.1569949204232; Tue, 01 Oct 2019 10:00:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569949204; cv=none; d=google.com; s=arc-20160816; b=bfiP5FxbJDnT7e2I0EkhlIMTiqd0li0b7+gPhuzI+Q1MKwaiHVgQIVD2203++lLDE8 0jUF3E7sD21uW4FZci+cSITuNn24u0/nFBflDEy5IgDrvMYd+I/9lIS5r5DTd9G0KeKa HYNQ5zU2bMNE8uB/vC+5KUeEYqmzyrViXyr9+MOUTdM2hK0bUFWXoZpaS011J9l7lKqm gE9fQTfSvu15oZIpuQ+oQeWm+wyF4fs27BOLRA+rXlmEGdO1Pqv0owRyrGQh662tPAby vDTAJF0j2eDnZQVUQ3ZZDzMAPfiLsnTOsgKv2UOPa0ts46ZvVCCC4bT87NgYLvVcu5E3 xebg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=8LmK8oEAhpqlJWmbrhfcC3/e3zJk6S+Y2OVTXCW5sfk=; b=vDRB4VJcY1bQbbgoFhcMuOdXH10/8LvajD3DXH0chX7FDPn445S36WrPNhn79RaMGZ 0kjm3TzY0+dmOrT/lr86ux4PNThfmwKbu+DFrGK6kj/ogc/OWGEpdir+A0DTc9n88/lo gCMVCn10LYkAdmXpcL9hjycgMNrnhmK/SLeZ8Pm6r3S12WMVwF68v++vN6AzuVRLtePg pLHhTD9R+R5mFSP2js7CtRaYKabuxYAn+U1T8uaQ5LYJkW6SZky0ZnJI9XSMlCxjCfcJ 2mtzWGd89sIQmRwYMsAn5hCbndaVrkHd3m9gIARIxYLBjZMWO279V7pWixlmySi6yP7F 8kdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g9si9552837edg.58.2019.10.01.09.59.39; Tue, 01 Oct 2019 10:00:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387876AbfJAQ6E (ORCPT + 99 others); Tue, 1 Oct 2019 12:58:04 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:49568 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731314AbfJAQlq (ORCPT ); Tue, 1 Oct 2019 12:41:46 -0400 Received: from localhost (unknown [IPv6:2601:601:9f00:1e2::3d5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 2241015458711; Tue, 1 Oct 2019 09:41:45 -0700 (PDT) Date: Tue, 01 Oct 2019 09:41:44 -0700 (PDT) Message-Id: <20191001.094144.1520493336302505890.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 From: David Miller In-Reply-To: References: <2CCD0856-433E-4602-A079-9F7F5F2E00D6@aosc.io> <20191001.093000.372726574458067639.davem@davemloft.net> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 01 Oct 2019 09:41:45 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Icenowy Zheng 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.