[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200725213226.hknk62rdovm3nmrz@skbuf>
Date: Sun, 26 Jul 2020 00:32:26 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: Richard Cochran <richardcochran@...il.com>
Cc: Jacob Keller <jacob.e.keller@...el.com>, kuba@...nel.org,
davem@...emloft.net, netdev@...r.kernel.org, sorganov@...il.com,
linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next 3/3] docs: networking: timestamping: add a set
of frequently asked questions
On Tue, Jul 21, 2020 at 08:25:53PM -0700, Richard Cochran wrote:
> On Tue, Jul 21, 2020 at 10:51:27PM +0300, Vladimir Oltean wrote:
> > So I think the position of "just don't have software timestamping code
> > in DSA and you'll be fine" won't be getting us anywhere. Either you can
> > or you can't, and there isn't anything absurd about it, so sooner or
> > later somebody will want to do it. The rules surrounding it, however,
> > are far from being ready, or clear.
> >
> > Am I missing something?
>
> I'm just trying to make things easy for you, as the author of DSA
> drivers. There is no need to set skb flags that have no purpose
> within the stack.
>
> Nobody is demanding software time stamps from any DSA devices yet, and
> so I don't see the point in solving a problem that doesn't exist.
>
> I'm sorry if the "rules" are not clear, but if you look around the
> kernel internals, you will be hard pressed to find perfectly
> documented rules anywhere!
>
> Thanks,
> Richard
Could we perhaps take a step back and see what can be improved about the
documentation updates?
Thanks,
-Vladimir
Powered by blists - more mailing lists