All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@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, kuba@kernel.org, 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 net-next v6 0/3] Add reset deassertion for Aspeed MDIO
Date: Thu, 28 Apr 2022 08:00:13 +0000	[thread overview]
Message-ID: <165113281383.18320.4392733597031620759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220427035501.17500-1-dylan_hung@aspeedtech.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 27 Apr 2022 11:54:58 +0800 you 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.
> 
> V6:
> - fix merge conflict for net-next
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/3] dt-bindings: net: add reset property for aspeed, ast2600-mdio binding
    https://git.kernel.org/netdev/net-next/c/65e42ad98e22
  - [net-next,v6,2/3] net: mdio: add reset control for Aspeed MDIO
    https://git.kernel.org/netdev/net-next/c/1585362250fe
  - [net-next,v6,3/3] ARM: dts: aspeed: add reset properties into MDIO nodes
    https://git.kernel.org/netdev/net-next/c/a8db203db05c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@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, kuba@kernel.org, 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 net-next v6 0/3] Add reset deassertion for Aspeed MDIO
Date: Thu, 28 Apr 2022 08:00:13 +0000	[thread overview]
Message-ID: <165113281383.18320.4392733597031620759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220427035501.17500-1-dylan_hung@aspeedtech.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 27 Apr 2022 11:54:58 +0800 you 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.
> 
> V6:
> - fix merge conflict for net-next
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/3] dt-bindings: net: add reset property for aspeed, ast2600-mdio binding
    https://git.kernel.org/netdev/net-next/c/65e42ad98e22
  - [net-next,v6,2/3] net: mdio: add reset control for Aspeed MDIO
    https://git.kernel.org/netdev/net-next/c/1585362250fe
  - [net-next,v6,3/3] ARM: dts: aspeed: add reset properties into MDIO nodes
    https://git.kernel.org/netdev/net-next/c/a8db203db05c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-04-28  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  3:54 [PATCH net-next v6 0/3] Add reset deassertion for Aspeed MDIO Dylan Hung
2022-04-27  3:54 ` Dylan Hung
2022-04-27  3:54 ` [PATCH net-next v6 1/3] dt-bindings: net: add reset property for aspeed, ast2600-mdio binding Dylan Hung
2022-04-27  3:54   ` Dylan Hung
2022-04-27  3:55 ` [PATCH net-next v6 2/3] net: mdio: add reset control for Aspeed MDIO Dylan Hung
2022-04-27  3:55   ` Dylan Hung
2022-04-27  3:55 ` [PATCH net-next v6 3/3] ARM: dts: aspeed: add reset properties into MDIO nodes Dylan Hung
2022-04-27  3:55   ` Dylan Hung
2022-04-28  8:00 ` patchwork-bot+netdevbpf [this message]
2022-04-28  8:00   ` [PATCH net-next v6 0/3] Add reset deassertion for Aspeed MDIO patchwork-bot+netdevbpf

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=165113281383.18320.4392733597031620759.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@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=kuba@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.