[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220328214522.7cfdff1e@kernel.org>
Date: Mon, 28 Mar 2022 21:45:22 -0700
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>, <BMC-SW@...eedtech.com>
Subject: Re: [PATCH v3 0/3] Add reset deassertion for Aspeed MDIO
On Fri, 25 Mar 2022 12:14:48 +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.
# Form letter - net-next is closed
We have already sent the networking pull request for 5.18
and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 5.18-rc1 is cut, in ~1 week.
RFC patches sent for review only are obviously welcome at any time.
Powered by blists - more mailing lists