From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: <netdev@vger.kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH net-next 0/4] netfilter updates for net-next
Date: Thu, 30 Mar 2023 23:44:02 -0700 [thread overview]
Message-ID: <20230330234402.0c618493@kernel.org> (raw)
In-Reply-To: <20230330202928.28705-1-fw@strlen.de>
On Thu, 30 Mar 2023 22:29:24 +0200 Florian Westphal wrote:
> are available in the Git repository at:
>
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next
Could you resend with a https link and a signed tag? :(
next prev parent reply other threads:[~2023-03-31 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 20:29 [PATCH net-next 0/4] netfilter updates for net-next Florian Westphal
2023-03-30 20:29 ` [PATCH net-next 1/4] netfilter: nfnetlink_log: remove rcu_bh usage Florian Westphal
2023-03-30 20:29 ` [PATCH net-next 2/4] netfilter: nfnetlink_queue: enable classid socket info retrieval Florian Westphal
2023-03-30 20:29 ` [PATCH net-next 3/4] netfilter: Correct documentation errors in nf_tables.h Florian Westphal
2023-03-30 20:29 ` [PATCH net-next 4/4] netfilter: ctnetlink: Support offloaded conntrack entry deletion Florian Westphal
2023-03-31 6:44 ` Jakub Kicinski [this message]
2023-03-31 10:48 ` [GIT PULL] netfilter updates for net-next 2023-03-30 Florian Westphal
2023-03-31 17:50 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 14:48 [PATCH net-next 0/4] netfilter updates for net-next Florian Westphal
2025-07-10 0:46 [PATCH net-next 0/4] Netfilter " Pablo Neira Ayuso
2026-01-22 16:29 [PATCH net-next 0/4] netfilter: " Florian Westphal
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=20230330234402.0c618493@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.