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;
Date:   Tue, 17 Mar 2020 21:02:20 -0700 (PDT)
Message-Id: <20200317.210220.1278270199388080239.davem@davemloft.net>
To:     opendmb@gmail.com
Cc:     f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: bcmgenet: revisit MAC reset
From:   David Miller <davem@davemloft.net>
In-Reply-To: <1584395096-41674-1-git-send-email-opendmb@gmail.com>
References: <1584395096-41674-1-git-send-email-opendmb@gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Doug Berger <opendmb@gmail.com>
Date: Mon, 16 Mar 2020 14:44:54 -0700

> Commit 3a55402c9387 ("net: bcmgenet: use RGMII loopback for MAC 
> reset") was intended to resolve issues with reseting the UniMAC
> core within the GENET block by providing better control over the
> clocks used by the UniMAC core. Unfortunately, it is not
> compatible with all of the supported system configurations so an
> alternative method must be applied.
> 
> This commit set provides such an alternative. The first commit
> reverts the previous change and the second commit provides the
> alternative reset sequence that addresses the concerns observed
> with the previous implementation.
> 
> This replacement implementation should be applied to the stable
> branches wherever commit 3a55402c9387 ("net: bcmgenet: use RGMII 
> loopback for MAC reset") has been applied.
> 
> Unfortunately, reverting that commit may conflict with some
> restructuring changes introduced by commit 4f8d81b77e66 ("net: 
> bcmgenet: Refactor register access in bcmgenet_mii_config").
> The first commit in this set has been manually edited to
> resolve the conflict on net/master. I would be happy to help
> stable maintainers with resolving any such conflicts if they
> occur. However, I do not expect that commit to have been
> backported to stable branch so hopefully the revert can be
> applied cleanly.

Series applied and queued up for -stable, thank you.