From: Richard Cochran <richardcochran@gmail.com>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: yangbo.lu@nxp.com, David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
mlichvar@redhat.com,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time
Date: Tue, 8 Mar 2022 12:52:09 -0800 [thread overview]
Message-ID: <20220308205209.GC16895@hoboy.vegasvil.org> (raw)
In-Reply-To: <CANr-f5yecFHG9mjRTd4aKBNzKgVV_tbZ4VAKXkMe2qxAMb66Gg@mail.gmail.com>
On Tue, Mar 08, 2022 at 08:49:03PM +0100, Gerhard Engleder wrote:
> 3 of 8 flags are unused in tx_flags. It may be possible to use the same flag for
> TX and RX. Is it worth it trying to save flags?
Yes, every bit is precious.
Thanks,
Richard
next prev parent reply other threads:[~2022-03-08 20:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 8:56 [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 1/6] bpf: Access hwtstamp field of hwtstamps directly Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 2/6] ptp: Initialize skb_shared_hwtstamps Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 3/6] ptp: Add free running time support Gerhard Engleder
2022-03-06 16:36 ` Richard Cochran
2022-03-06 8:56 ` [RFC PATCH net-next 4/6] ptp: Support time stamps based on free running time Gerhard Engleder
2022-03-06 16:42 ` Richard Cochran
2022-03-06 8:56 ` [RFC PATCH net-next 5/6] ptp: Allow vclocks without free running physical clock Gerhard Engleder
2022-03-06 8:56 ` [RFC PATCH net-next 6/6] tsnep: Add free running time support Gerhard Engleder
2022-03-06 16:49 ` [RFC PATCH net-next 0/6] ptp: Support hardware clocks with additional free running time Richard Cochran
2022-03-06 16:53 ` Richard Cochran
2022-03-06 17:05 ` Richard Cochran
2022-03-06 18:38 ` Gerhard Engleder
2022-03-06 21:50 ` Richard Cochran
2022-03-07 14:34 ` Richard Cochran
2022-03-07 17:54 ` Gerhard Engleder
2022-03-07 21:30 ` Richard Cochran
2022-03-08 0:55 ` Richard Cochran
2022-03-08 19:49 ` Gerhard Engleder
2022-03-08 20:52 ` Richard Cochran [this message]
2022-03-08 0:57 ` Richard Cochran
2022-03-07 12:07 ` Michael Walle
2022-03-07 14:05 ` Richard Cochran
2022-03-07 14:23 ` Miroslav Lichvar
2022-03-07 14:37 ` Richard Cochran
2022-03-08 20:55 ` Richard Cochran
2022-03-07 16:01 ` Gerhard Engleder
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=20220308205209.GC16895@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=gerhard@engleder-embedded.com \
--cc=kuba@kernel.org \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=yangbo.lu@nxp.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.