From: patchwork-bot+netdevbpf@kernel.org
To: Jon Hunter <jonathanh@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
f.fainelli@gmail.com, olteanv@gmail.com, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, joabreu@synopsys.com,
netdev@vger.kernel.org, linux-tegra@vger.kernel.org,
ruppala@nvidia.com
Subject: Re: [PATCH V6 1/2] net: stmmac: Power up SERDES after the PHY link
Date: Mon, 05 Dec 2022 09:50:16 +0000 [thread overview]
Message-ID: <167023381671.8030.2390834995208845499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221201155844.43217-1-jonathanh@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 1 Dec 2022 15:58:43 +0000 you wrote:
> From: Revanth Kumar Uppala <ruppala@nvidia.com>
>
> The Tegra MGBE ethernet controller requires that the SERDES link is
> powered-up after the PHY link is up, otherwise the link fails to
> become ready following a resume from suspend. Add a variable to indicate
> that the SERDES link must be powered-up after the PHY link.
>
> [...]
Here is the summary with links:
- [V6,1/2] net: stmmac: Power up SERDES after the PHY link
https://git.kernel.org/netdev/net-next/c/a46e90101242
- [V6,2/2] net: stmmac: tegra: Add MGBE support
https://git.kernel.org/netdev/net-next/c/d8ca113724e7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-05 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 15:58 [PATCH V6 1/2] net: stmmac: Power up SERDES after the PHY link Jon Hunter
2022-12-01 15:58 ` [PATCH V6 2/2] net: stmmac: tegra: Add MGBE support Jon Hunter
2022-12-05 9:50 ` patchwork-bot+netdevbpf [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=167023381671.8030.2390834995208845499.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=ruppala@nvidia.com \
/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