From: Jakub Kicinski <kuba@kernel.org>
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: <robh+dt@kernel.org>, <joel@jms.id.au>, <andrew@aj.id.au>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <pabeni@redhat.com>,
<p.zabel@pengutronix.de>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <krzk+dt@kernel.org>,
<BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v5 0/3] Add reset deassertion for Aspeed MDIO
Date: Thu, 14 Apr 2022 14:22:12 +0200 [thread overview]
Message-ID: <20220414142212.258fcb37@kernel.org> (raw)
In-Reply-To: <20220413121037.23748-1-dylan_hung@aspeedtech.com>
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?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: <robh+dt@kernel.org>, <joel@jms.id.au>, <andrew@aj.id.au>,
<andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
<davem@davemloft.net>, <pabeni@redhat.com>,
<p.zabel@pengutronix.de>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <krzk+dt@kernel.org>,
<BMC-SW@aspeedtech.com>
Subject: Re: [PATCH v5 0/3] Add reset deassertion for Aspeed MDIO
Date: Thu, 14 Apr 2022 14:22:12 +0200 [thread overview]
Message-ID: <20220414142212.258fcb37@kernel.org> (raw)
In-Reply-To: <20220413121037.23748-1-dylan_hung@aspeedtech.com>
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?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-14 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 12:10 [PATCH v5 0/3] Add reset deassertion for Aspeed MDIO Dylan Hung
2022-04-13 12:10 ` Dylan Hung
2022-04-13 12:10 ` [PATCH v5 1/3] dt-bindings: net: add reset property for aspeed, ast2600-mdio binding Dylan Hung
2022-04-13 12:10 ` Dylan Hung
2022-04-13 12:10 ` [PATCH v5 2/3] net: mdio: add reset control for Aspeed MDIO Dylan Hung
2022-04-13 12:10 ` Dylan Hung
2022-04-13 12:10 ` [PATCH v5 3/3] ARM: dts: aspeed: add reset properties into MDIO nodes Dylan Hung
2022-04-13 12:10 ` Dylan Hung
2022-04-14 12:22 ` Jakub Kicinski [this message]
2022-04-14 12:22 ` [PATCH v5 0/3] Add reset deassertion for Aspeed MDIO Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220414142212.258fcb37@kernel.org \
--to=kuba@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=hkallweit1@gmail.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.