[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd270cc5-607b-0ec2-f5c4-15895067ffe1@intel.com>
Date: Wed, 17 May 2023 12:58:43 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Köry Maincent <kory.maincent@...tlin.com>, Jakub Kicinski
<kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <glipus@...il.com>,
<maxime.chevallier@...tlin.com>, <vladimir.oltean@....com>,
<vadim.fedorenko@...ux.dev>, <richardcochran@...il.com>,
<gerhard@...leder-embedded.com>, <thomas.petazzoni@...tlin.com>,
<krzysztof.kozlowski+dt@...aro.org>, <robh+dt@...nel.org>,
<linux@...linux.org.uk>
Subject: Re: [PATCH net-next RFC v4 2/5] net: Expose available time stamping
layers to user space.
On 4/7/2023 1:58 AM, Köry Maincent wrote:
> On Thu, 6 Apr 2023 18:46:46 -0700
>> What does SOF_ stand for? 🤔️
>
> It was to follow the naming reference in
> "Documentation/networking/timestamping.rst" like SOF_TIMESTAMPING_RX_HARDWARE
> or SOF_TIMESTAMPING_RX_SOFTAWRE but indeed I do not really understand the SOF
> prefix. SocketF?
>
I believe its something like "Socket Option Flag" or "Socket Option
Feature", but it is pretty old, so I don't really remember full context.
Thanks,
Jake
Powered by blists - more mailing lists