From: patchwork-bot+netdevbpf@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, geert+renesas@glider.be,
linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, biju.das.jz@bp.renesas.com,
fabrizio.castro.jz@renesas.com,
prabhakar.mahadev-lad.rj@bp.renesas.com, lkft@linaro.org
Subject: Re: [PATCH net-next] net: pcs: Kconfig: Fix unmet dependency warning
Date: Wed, 17 Sep 2025 22:20:26 +0000 [thread overview]
Message-ID: <175814762624.2168096.4750691508233260895.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916162335.3339558-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 Sep 2025 17:23:35 +0100 you wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Fix the Kconfig dependencies for PCS_RZN1_MIIC to avoid the unmet direct
> dependency warning when enabling DWMAC_RENESAS_GBETH. The PCS driver is
> used on multiple Renesas SoCs including RZ/N1, RZ/N2H and RZ/T2H, but the
> existing condition only allowed ARCH_RZN1, ARCH_R9A09G077, or
> ARCH_R9A09G087. This conflicted with the GBETH/GMAC driver which selects
> PCS_RZN1_MIIC under ARCH_RENESAS.
>
> [...]
Here is the summary with links:
- [net-next] net: pcs: Kconfig: Fix unmet dependency warning
https://git.kernel.org/netdev/net-next/c/dfc85640796b
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:[~2025-09-17 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 16:23 [PATCH net-next] net: pcs: Kconfig: Fix unmet dependency warning Prabhakar
2025-09-17 8:05 ` Geert Uytterhoeven
2025-09-17 22:20 ` 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=175814762624.2168096.4750691508233260895.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkft@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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