From: patchwork-bot+netdevbpf@kernel.org
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, s.shtylyov@omp.ru,
prabhakar.mahadev-lad.rj@bp.renesas.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, geert+renesas@glider.be,
Chris.Paterson2@renesas.com, biju.das@bp.renesas.com
Subject: Re: [PATCH net-next v5] ravb: Add RZ/G2L MII interface support
Date: Tue, 20 Sep 2022 15:50:16 +0000 [thread overview]
Message-ID: <166368901622.16825.11625479930549195610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220914192604.265859-1-biju.das.jz@bp.renesas.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Sep 2022 20:26:04 +0100 you wrote:
> EMAC IP found on RZ/G2L Gb ethernet supports MII interface.
> This patch adds support for selecting MII interface mode.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v4->v5:
> * Reorderd enum CXR35_BIT from LSB to MSB
> v3->v4:
> * Dropped CXR35_HALFCYC_CLKSW1000 enum
> * Added CXR35_HALFCYC_CLKSW, CXR35_SEL_XMII and CXR35_SEL_XMII_RGMII
> enum.
> v2->v3:
> * Documented CXR35_HALFCYC_CLKSW1000 and CXR35_SEL_XMII_MII enum.
> v1->v2:
> * Fixed spaces->Tab around CXR35 description.
>
> [...]
Here is the summary with links:
- [net-next,v5] ravb: Add RZ/G2L MII interface support
https://git.kernel.org/netdev/net-next/c/1089877ada8d
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-09-20 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 19:26 [PATCH net-next v5] ravb: Add RZ/G2L MII interface support Biju Das
2022-09-15 16:14 ` Sergey Shtylyov
2022-09-20 15: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=166368901622.16825.11625479930549195610.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
/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).