From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21A73C433DB for ; Fri, 8 Jan 2021 12:39:44 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8A54D235FF for ; Fri, 8 Jan 2021 12:39:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8A54D235FF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=armlinux.org.uk Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=PyYpSr7Ytl0LyXi5qweYIMxEcpJK+BfdxW03fhCOnBs=; b=kWSmiI7bg17vFl1Y+vL7iN7g5 JcXnB5wjlBqPAODpANhrUEdH42ACKIiaHU85UH5lkFROTUvTnB19YDZUl3uOZTlaD0aM8FUoA4Qey RF7UfOk2t8LCNN9xagnlP1LJseUNIkbI3DprdfR5EjdX11706L6ENSFwyS+DbVRRKg9hstfrrFotu XuiHFQMmBmLmffPPuXH2sQJsEYOBZawRbLkfKK3V3Q4cgy+KkO0Rcxl7qxWtazq/23XzFo75jRqdx JUBytxqcAtZfkC5f451b6dUYaSvY8fhgO1Z9RV9IPAW+DIKUlXfjgyc3hLjYlyUUrsNQQVt6AIf9R KmK3xTuRw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kxr1X-0008G4-Dr; Fri, 08 Jan 2021 12:37:47 +0000 Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:32c8:5054:ff:fe00:142]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kxr16-0008DR-T0 for linux-arm-kernel@lists.infradead.org; Fri, 08 Jan 2021 12:37:23 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=d8mhMVa/UrQjc1fJdOk/GbI+6P3P1J56ZdhJJ/isn+U=; b=ZJM65vK10HjREKJ6XfNnwtGr5 WiPCgssjAlHUZwlSrsfKZOZOwPfZIMmbR6vRkAeXbbBS8c5GaRIJrWANL5y7tITqKjNFAWBZ+kgHt 1NEhr92pyQDPSwsOv2wu0AqGya1VF/qXKlxCcKavTA9k4AiHssjYj9hugv7uPt5jUr3uhMF535EWY BBM7RdFuB3iaVCmuded5mXbXIk7NErN7NDUI70dey0vJsQEQmInFkJn0WjCaeH6nLLmf0QdVMpFI9 p34xvaT6vwTU++GNcJA0HSwFhS/KsU3LkFTHu40+RsWDoS4U1fUJxhDB/Zf7aqrdr9xAkx/GJlFvw M5J3KGJaw==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:45304) by pandora.armlinux.org.uk with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kxr13-00041r-5e; Fri, 08 Jan 2021 12:37:17 +0000 Received: from linux by shell.armlinux.org.uk with local (Exim 4.92) (envelope-from ) id 1kxr12-00029S-NA; Fri, 08 Jan 2021 12:37:16 +0000 Date: Fri, 8 Jan 2021 12:37:16 +0000 From: Russell King - ARM Linux admin To: Michael Walle Subject: Re: Broken ethernet on SolidRun cubox-i Message-ID: <20210108123716.GX1551@shell.armlinux.org.uk> References: <2ae000163aa34b963dd387c824bdc3c9@walle.cc> <20201226123421.GD1551@shell.armlinux.org.uk> <1d79aa88e73b6e0118e570a64026817e@walle.cc> <20201227161114.GF1551@shell.armlinux.org.uk> <20210108115357.GU1551@shell.armlinux.org.uk> <6e3ae1175c71cd27f7578071a801a4fc@walle.cc> <20210108120148.GV1551@shell.armlinux.org.uk> <1ed4a0ffc17a827240706ed3fa28cd2a@walle.cc> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1ed4a0ffc17a827240706ed3fa28cd2a@walle.cc> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210108_073720_989860_9A177CF6 X-CRM114-Status: GOOD ( 20.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Matus Ujhelyi , acmattheis@gmx.net, Christoph Mattheis , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Jan 08, 2021 at 01:14:19PM +0100, Michael Walle wrote: > Am 2021-01-08 13:01, schrieb Russell King - ARM Linux admin: > > This sounds like a mess of indirection. What is "Christophs dtb"? > > Why are there different dtbs out there for the same platform? If > > there's changes necessary, why aren't they being submitted to the > > mainline kernel? > > > > In fact, why aren't users reporting these problems to mainline kernel > > developers? Why do we have to have this tortuous bug reporting route > > which makes testing fixes difficult? > > > > This rather makes me not want to care about this. > > Well first it was a suspected issue with 'my' change in the Atheros > PHY driver, which turned out to be not the case. I _voluntarily_ > tried to debug the issue with a user (Christoph) just to find out > that it is likely caused by the commit mentioned above. So for > startes, why would I care? I just wanted to be kind and provide > some help. If anything, this shows me, I should rather stick to > my own problems. > > So please advise Christoph, where he should report this bug. There is, unfortunately, a long history where the appropriate kernel developers have had no knowledge of bugs that have been introduced by changes that have been made, simply because users report them on things like web forums or other mailing lists. In the normal process of things, the bugs have only found out about years later, maybe when someone finally contacts the appropriate kernel developers pointing out the problem. A case in point was the removal of bogomips from /proc/cpuinfo, which resulted in kernel developers being roasted by Linus when it was pointed out that users had been reporting the problem on forums for over a year. Apparently, it was _our_ fault for not knowing about them. Similar seems to be happening with my SFP work - it seems people would much rather report problems on random forums around the Internet rather than send an email to anyone who can fix the problem in mainline kernels. Kernel development is fundamentally a difficult, frustrating and depressing activity. -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel