Subject: Re: [PATCH net-next] net/tcp_sigpool: Enable compile-testing

From: Simon Horman <[email-masked]>
Date: Tue, 9 Dec 2025 19:24:11 +0000

On Thu, Dec 04, 2025 at 03:57:31PM +0100, Geert Uytterhoeven wrote:
> Since commit 37a183d3b7cdb873 ("tcp: Convert tcp-md5 to use MD5 library
> instead of crypto_ahash"), TCP_SIGPOOL is only selected by TCP_AO.
> However, the latter depends on 64BIT, so tcp_sigpool can no longer be
> built on 32-bit platforms at all.
> 
> Improve compile coverage on 32-bit by allowing the user to enable
> TCP_SIGPOOL when compile-testing.  Add a dependency on CRYPTO, which is
> always fulfilled when selected by TCP_AO.
> 
> Signed-off-by: Geert Uytterhoeven <[email-masked]>
> ---
> One remaining oddity is that TCP_SIGPOOL has always been a tristate
> symbol, while all users that select it have always been boolean symbols.
> I kept that as-is, as it builds fine as a module.

Hi Geert,

I tested some of the COMPILE_TEST/TCP_AO
combinations and this seems to work as expected.

Reviewed-by: Simon Horman <[email-masked]>

However,

## Form letter - net-next-closed

The merge window for v6.19 has begun and therefore net-next has closed
for new drivers, features, code refactoring and optimizations. We are
currently accepting bug fixes only.

Please repost when net-next reopens.

Due to a combination of the merge-window, travel commitments of the
maintainers, and the holiday season, net-next will re-open after
2nd January.

RFC patches sent for review only are welcome at any time.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle

-- 
pw-bot: defer