From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
David Ahern <dsahern@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Xin Long <lucien.xin@gmail.com>
Cc: Geliang Tang <tanggeliang@kylinos.cn>,
netdev@vger.kernel.org, mptcp@lists.linux.dev,
linux-sctp@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] add sock_kmemdup helper
Date: Fri, 28 Feb 2025 13:06:41 +0100 [thread overview]
Message-ID: <1ce1c600-72db-4a95-86a3-c881f5b75a56@kernel.org> (raw)
In-Reply-To: <cover.1740735165.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 28/02/2025 11:01, Geliang Tang wrote:
> v2:
> - add "EXPORT_SYMBOL(sock_kmemdup)" as Matthieu suggested.
> - drop the patch "use sock_kmemdup for tcp_ao_key".
Thank you for the v2!
For the modifications in MPTCP code, this looks OK to me:
Acked-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2025-02-28 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 10:01 [PATCH net-next v2 0/3] add sock_kmemdup helper Geliang Tang
2025-02-28 10:01 ` [PATCH net-next v2 1/3] sock: " Geliang Tang
2025-03-03 23:16 ` Kuniyuki Iwashima
2025-02-28 10:01 ` [PATCH net-next v2 2/3] net: use sock_kmemdup for ip_options Geliang Tang
2025-03-03 23:18 ` Kuniyuki Iwashima
2025-02-28 10:01 ` [PATCH net-next v2 3/3] mptcp: use sock_kmemdup for address entry Geliang Tang
2025-02-28 11:08 ` [PATCH net-next v2 0/3] add sock_kmemdup helper MPTCP CI
2025-02-28 12:06 ` Matthieu Baerts [this message]
2025-03-04 2:10 ` patchwork-bot+netdevbpf
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=1ce1c600-72db-4a95-86a3-c881f5b75a56@kernel.org \
--to=matttbe@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=martineau@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tanggeliang@kylinos.cn \
--cc=willemb@google.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.