[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240701162621.GB596879@kernel.org>
Date: Mon, 1 Jul 2024 17:26:21 +0100
From: Simon Horman <horms@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
NetFilter <netfilter-devel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the ipvs-next tree
On Mon, Jul 01, 2024 at 03:39:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the netfilter-next tree as a different
> commit (but the same patch):
>
> 8871d1e4dceb ("netfilter: xt_recent: Lift restrictions on max hitcount value")
>
> This is commit
>
> f4ebd03496f6 ("netfilter: xt_recent: Lift restrictions on max hitcount value")
>
> in the netfilter-next tree.
Thanks Stephen,
I have force-pushed ipvs-next so that it should now mach netfilter-next.
I think this should resolve the problem above.
Powered by blists - more mailing lists