netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, willemdebruijn.kernel@gmail.com,
	willemb@google.com, kuniyu@amazon.com, netdev@vger.kernel.org,
	kernelxing@tencent.com
Subject: Re: [PATCH net-next v4] net-timestamp: namespacify the sysctl_tstamp_allow_data
Date: Tue, 08 Oct 2024 23:20:37 +0000	[thread overview]
Message-ID: <172842963773.718280.4117941839718863673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241005222609.94980-1-kerneljasonxing@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  6 Oct 2024 07:26:09 +0900 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
> 
> Let it be tuned in per netns by admins.
> 
> Signed-off-by: Jason Xing <kernelxing@tencent.com>
> ---
> v4
> Link: https://lore.kernel.org/all/20241003104035.22374-1-kerneljasonxing@gmail.com/
> 1. use u8 instead of int to save more bytes (Kuniyuki)
> 
> [...]

Here is the summary with links:
  - [net-next,v4] net-timestamp: namespacify the sysctl_tstamp_allow_data
    https://git.kernel.org/netdev/net-next/c/da5e06dee58a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-10-08 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 22:26 [PATCH net-next v4] net-timestamp: namespacify the sysctl_tstamp_allow_data Jason Xing
2024-10-06 15:30 ` Kuniyuki Iwashima
2024-10-06 18:54 ` Eric Dumazet
2024-10-06 23:50 ` Willem de Bruijn
2024-10-08 23:20 ` patchwork-bot+netdevbpf [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=172842963773.718280.4117941839718863673.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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 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 NNTP newsgroup(s).