| Message ID | 20240215170508.3402883-1-leitao@debian.org (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | ea7f3cfaa58873bbe271577efa800647e30f18bd |
| Delegated to: | Netdev Maintainers |
| Headers | show |
| Series | [net-next] net: bql: allow the config to be disabled | expand |
Hello: This patch was applied to netdev/net-next.git (main) by David S. Miller <davem@davemloft.net>: On Thu, 15 Feb 2024 09:05:07 -0800 you wrote: > It is impossible to disable BQL individually today, since there is no > prompt for the Kconfig entry, so, the BQL is always enabled if SYSFS is > enabled. > > Create a prompt entry for BQL, so, it could be enabled or disabled at > build time independently of SYSFS. > > [...] Here is the summary with links: - [net-next] net: bql: allow the config to be disabled https://git.kernel.org/netdev/net-next/c/ea7f3cfaa588 You are awesome, thank you!
diff --git a/net/Kconfig b/net/Kconfig index 4adc47d0c9c2..3e57ccf0da27 100644 --- a/net/Kconfig +++ b/net/Kconfig @@ -331,6 +331,7 @@ config NET_RX_BUSY_POLL config BQL bool + prompt "Enable Byte Queue Limits" depends on SYSFS select DQL default y
It is impossible to disable BQL individually today, since there is no prompt for the Kconfig entry, so, the BQL is always enabled if SYSFS is enabled. Create a prompt entry for BQL, so, it could be enabled or disabled at build time independently of SYSFS. Signed-off-by: Breno Leitao <leitao@debian.org> --- net/Kconfig | 1 + 1 file changed, 1 insertion(+)