From: Simon Horman <horms@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
NetFilter <netfilter-devel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the ipvs-next tree
Date: Mon, 1 Jul 2024 17:26:21 +0100 [thread overview]
Message-ID: <20240701162621.GB596879@kernel.org> (raw)
In-Reply-To: <20240701153915.317fc7a2@canb.auug.org.au>
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.
prev parent reply other threads:[~2024-07-01 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 5:39 linux-next: duplicate patch in the ipvs-next tree Stephen Rothwell
2024-07-01 16:26 ` Simon Horman [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=20240701162621.GB596879@kernel.org \
--to=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sfr@canb.auug.org.au \
/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