[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220414142212.258fcb37@kernel.org>
Date: Thu, 14 Apr 2022 14:22:12 +0200
From: Jakub Kicinski <kuba@...nel.org>
To: Dylan Hung <dylan_hung@...eedtech.com>
Cc: <robh+dt@...nel.org>, <joel@....id.au>, <andrew@...id.au>,
<andrew@...n.ch>, <hkallweit1@...il.com>, <linux@...linux.org.uk>,
<davem@...emloft.net>, <pabeni@...hat.com>,
<p.zabel@...gutronix.de>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-aspeed@...ts.ozlabs.org>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>, <krzk+dt@...nel.org>,
<BMC-SW@...eedtech.com>
Subject: Re: [PATCH v5 0/3] Add reset deassertion for Aspeed MDIO
On Wed, 13 Apr 2022 20:10:34 +0800 Dylan Hung wrote:
> Add missing reset deassertion for Aspeed MDIO bus controller. The reset
> is asserted by the hardware when power-on so the driver only needs to
> deassert it. To be able to work with the old DT blobs, the reset is
> optional since it may be deasserted by the bootloader or the previous
> kernel.
I presume you want this applied to net-next, but it appears there
is a conflict or something. Could you resend the patches based on
net-next/master?
Powered by blists - more mailing lists