From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: ivecera@redhat.com, Prathosh.Satish@microchip.com,
jiri@resnulli.us, kuba@kernel.org, conor.dooley@microchip.com,
netdev@vger.kernel.org, linux-spi@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dpll: Make ZL3073X invisible
Date: Sat, 02 Aug 2025 00:14:12 +0000 [thread overview]
Message-ID: <175409365249.4093813.14032905204294437624.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <97804163aeb262f0e0706d00c29d9bb751844454.1753874405.git.geert+renesas@glider.be>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Jul 2025 13:23:32 +0200 you wrote:
> Currently, the user is always asked about the Microchip Azurite
> DPLL/PTP/SyncE core driver, even when I2C and SPI are disabled, and thus
> the driver cannot be used at all.
>
> Fix this by making the Kconfig symbol for the core driver invisible
> (unless compile-testing), and selecting it by the bus glue sub-drivers.
> Drop the modular defaults, as drivers should not default to enabled.
>
> [...]
Here is the summary with links:
- dpll: Make ZL3073X invisible
https://git.kernel.org/netdev/net/c/a4f0866e3dbb
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-08-02 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 11:23 [PATCH] dpll: Make ZL3073X invisible Geert Uytterhoeven
2025-08-01 11:17 ` Ivan Vecera
2025-08-02 0:14 ` 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=175409365249.4093813.14032905204294437624.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=conor.dooley@microchip.com \
--cc=geert+renesas@glider.be \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=netdev@vger.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.