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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 3A13FC433E0 for ; Fri, 26 Feb 2021 14:17:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0672F64D9F for ; Fri, 26 Feb 2021 14:17:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230175AbhBZORS (ORCPT ); Fri, 26 Feb 2021 09:17:18 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:60430 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230155AbhBZORC (ORCPT ); Fri, 26 Feb 2021 09:17:02 -0500 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1lFdue-008c0w-ES; Fri, 26 Feb 2021 15:16:12 +0100 Date: Fri, 26 Feb 2021 15:16:12 +0100 From: Andrew Lunn To: Daniel =?iso-8859-1?Q?Gonz=E1lez?= Cabanelas Cc: Heiner Kallweit , Florian Fainelli , "David S. Miller" , Jakub Kicinski , gregkh@linuxfoundation.org, netdev@vger.kernel.org, =?iso-8859-1?Q?=C1lvaro_Fern=E1ndez?= Rojas Subject: Re: [PATCH v2] bcm63xx_enet: fix internal phy IRQ assignment Message-ID: References: <0e75a5c3-f6bd-6039-3cfd-8708da963d20@gmail.com> <7fc4933f-36d4-99dc-f968-9ca3b8758a9b@gmail.com> <286fb043-b812-a5ba-c66e-eef63fe5cc98@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > > OK, I see. Then there's no reason to complain upstream. > > Either use the mainline B53 DSA driver of fix interrupt mode > > downstream. > > I agree. > > This b53 driver has one PHY with the same BCM63XX phy_id, causing a > double probe. I'll send the original patch to the OpenWrt project. Hi Daniel There is a bit of a disconnect between OpenWRT and Mainline. They have a lot of fixes that don't make it upstream. So it is good to see somebody trying to fix mainline first, and then backport to OpenWRT. But please do test mainline and confirm it is actually broken before submitting patches. When you do submit to OpenWRT, please make it clear this is an OpenWRT problem so somebody does not try to push it to mainline again.... And if you have an itch to scratch, try adding mainline support for this board. We can guide you. Andrew