From: Jason Xing <kerneljasonxing@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: edumazet@google.com, pablo@netfilter.org, kadlec@netfilter.org,
fw@strlen.de, pabeni@redhat.com, davem@davemloft.net,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack
Date: Tue, 12 Mar 2024 00:00:37 +0800 [thread overview]
Message-ID: <CAL+tcoAv=nBRyRVFhgKkAWu1v5Uhs4aNxBxTRPs5YE89R7sf-w@mail.gmail.com> (raw)
In-Reply-To: <20240311085632.2d0742e6@kernel.org>
On Mon, Mar 11, 2024 at 11:56 PM Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Mon, 11 Mar 2024 14:37:25 +0800 Jason Xing wrote:
> > I saw the status in patchwork was changed, but I've not received the
> > comments. So I spent some time learning how it works in the netfilter
> > area.
> >
> > I just noticed that there are two trees (nf and nf-next), so should I
> > target nf-next and resend this patch and another one[1]?
>
> I don't think you need to repost, you CCed the right people, they
> should be able to process the patches. But do keep in mind the
> netfilter trees on next patches.
Thanks for the clarification :)
prev parent reply other threads:[~2024-03-11 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:29 [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack Jason Xing
2024-03-08 9:29 ` [PATCH net-next] netfilter: conntrack: using NF_DROP in test statement in nf_conntrack_in() Jason Xing
2024-03-11 6:37 ` [PATCH net-next] netfilter: conntrack: dccp: try not to drop skb in conntrack Jason Xing
2024-03-11 15:56 ` Jakub Kicinski
2024-03-11 16:00 ` Jason Xing [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='CAL+tcoAv=nBRyRVFhgKkAWu1v5Uhs4aNxBxTRPs5YE89R7sf-w@mail.gmail.com' \
--to=kerneljasonxing@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).