From: David Miller <davem@davemloft.net>
To: andrew@aj.id.au
Cc: netdev@vger.kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
joel@jms.id.au, benh@kernel.crashing.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v2 0/3] net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs
Date: Fri, 11 Oct 2019 20:38:12 -0700 (PDT) [thread overview]
Message-ID: <20191011.203812.1828730130029996774.davem@davemloft.net> (raw)
In-Reply-To: <20191010020756.4198-1-andrew@aj.id.au>
From: Andrew Jeffery <andrew@aj.id.au>
Date: Thu, 10 Oct 2019 12:37:53 +1030
> This series slightly extends the devicetree binding and driver for the
> FTGMAC100 to describe an optional RMII RCLK gate in the clocks property.
> Currently it's necessary for the kernel to ungate RCLK on the AST2600 in NCSI
> configurations as u-boot does not yet support NCSI (which uses the
> R(educed)MII).
>
> v2:
> * Clear up Reduced vs Reversed MII in the cover letter
> * Mitigate anxiety in the commit message for 1/3
> * Clarify that AST2500 is also affected in the clocks property description in
> 2/3
> * Rework the error paths and update some comments in 3/3
>
> v1 can be found here: https://lore.kernel.org/netdev/20191008115143.14149-1-andrew@aj.id.au/
Series applied to net-next, thank you.
prev parent reply other threads:[~2019-10-12 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 2:07 [PATCH v2 0/3] net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs Andrew Jeffery
2019-10-10 2:07 ` [PATCH v2 1/3] dt-bindings: net: ftgmac100: Document AST2600 compatible Andrew Jeffery
2019-10-11 17:01 ` Rob Herring
2019-10-10 2:07 ` [PATCH v2 2/3] dt-bindings: net: ftgmac100: Describe clock properties Andrew Jeffery
2019-10-11 17:02 ` Rob Herring
2019-10-10 2:07 ` [PATCH v2 3/3] net: ftgmac100: Ungate RCLK for RMII on ASPEED MACs Andrew Jeffery
2019-10-10 23:44 ` Joel Stanley
2019-10-12 3:38 ` David Miller [this message]
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=20191011.203812.1828730130029996774.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).