From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Vadim Fedorenko <vadfed@meta.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Willem de Bruijn <willemb@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
Jason Xing <kerneljasonxing@gmail.com>,
Simon Horman <horms@kernel.org>
Cc: Vadim Fedorenko <vadfed@meta.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 2/3] net_tstamp: add SCM_TS_OPT_ID for RAW sockets
Date: Mon, 09 Sep 2024 13:48:29 -0400 [thread overview]
Message-ID: <66df34edd8464_3d030294fd@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20240909165046.644417-3-vadfed@meta.com>
Vadim Fedorenko wrote:
> The last type of sockets which supports SOF_TIMESTAMPING_OPT_ID is RAW
> sockets. To add new option this patch converts all callers (direct and
> indirect) of _sock_tx_timestamp to provide sockcm_cookie instead of
> tsflags. And while here fix __sock_tx_timestamp to receive tsflags as
> __u32 instead of __u16.
>
> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2024-09-09 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 16:50 [PATCH net-next v4 0/3] Add option to provide OPT_ID value via cmsg Vadim Fedorenko
2024-09-09 16:50 ` [PATCH net-next v4 1/3] net_tstamp: add SCM_TS_OPT_ID to provide OPT_ID in control message Vadim Fedorenko
2024-09-09 17:48 ` Willem de Bruijn
2024-09-09 16:50 ` [PATCH net-next v4 2/3] net_tstamp: add SCM_TS_OPT_ID for RAW sockets Vadim Fedorenko
2024-09-09 17:48 ` Willem de Bruijn [this message]
2024-09-10 7:05 ` kernel test robot
2024-09-10 7:47 ` kernel test robot
2024-09-09 16:50 ` [PATCH net-next v4 3/3] selftests: txtimestamp: add SCM_TS_OPT_ID test Vadim Fedorenko
2024-09-09 17:50 ` Willem de Bruijn
2024-09-09 19:59 ` Vadim Fedorenko
2024-09-09 20:31 ` Willem de Bruijn
2024-09-09 20:37 ` Vadim Fedorenko
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=66df34edd8464_3d030294fd@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=dsahern@kernel.org \
--cc=horms@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadfed@meta.com \
--cc=vadim.fedorenko@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox