Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Erez
On Wed, 14 Jun 2023 at 06:25, Richard Cochran wrote: > On Tue, Jun 13, 2023 at 01:01:11PM +0200, Erez wrote: > > > Just so I am clear on the matter. > > I simply suggest taking the same test you run with linuxptp-testsuite. > > And run it in a github action. So we can all run it before we send >

Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Martin Pecka
Once a commit lands in github, then it is too late. Not really - if you push to a fork of linuxptp. Which, you, Richard, probably won't, but everybody else could. Martin -- Mgr. Martin Pecka, Ph.D. Researcher at Vision for Robotics and Autonomous Systems group Faculty of Electrical Engineeri

Re: [Linuxptp-devel] [PATCH] Use messageLength field to detetmine suffix length

2023-06-13 Thread Richard Cochran
On Tue, Jun 13, 2023 at 12:57:10PM -0400, Dylan Robinson wrote: > Definitely. In the audio space where I work there are many examples of > this. I have seen how being first to market and having wide adoption can > end up turning "improper" implementations into a de facto standard. > Based on my re

Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Richard Cochran
On Tue, Jun 13, 2023 at 01:01:11PM +0200, Erez wrote: > Just so I am clear on the matter. > I simply suggest taking the same test you run with linuxptp-testsuite. > And run it in a github action. So we can all run it before we send patches. > In addition to the tests you run :-) I run the tests _

Re: [Linuxptp-devel] [PATCH] Use messageLength field to detetmine suffix length

2023-06-13 Thread Dylan Robinson
Hi Erez, Thanks for the note. On Mon, 12 Jun 2023 21:14:17 +0200, Erez wrote: > This is not the only standard that follows the market and existing > products. > It happens everywhere. > I do not suggest to ignore standards, > Only bear in mind that we can not rely on others to implement the > sta

Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Erez
On Tue, 13 Jun 2023 at 12:57, Erez wrote: > > > On Tue, 13 Jun 2023 at 09:48, Richard Cochran > wrote: > >> On Tue, Jun 13, 2023 at 08:02:29AM +0200, Erez wrote: >> > Hi, >> > >> > Using Miroslav's linuxptp-testsuite we can run a simulated HIL in github >> > itself. >> >> "Simulated HIL" is an o

Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Erez
On Tue, 13 Jun 2023 at 09:48, Richard Cochran wrote: > On Tue, Jun 13, 2023 at 08:02:29AM +0200, Erez wrote: > > Hi, > > > > Using Miroslav's linuxptp-testsuite we can run a simulated HIL in github > > itself. > > "Simulated HIL" is an oxymoron. H stand for hardware. > Simulation of hardware, t

Re: [Linuxptp-devel] [Linuxptp-users] Quarterly release schedule

2023-06-13 Thread Richard Cochran
On Tue, Jun 13, 2023 at 08:02:29AM +0200, Erez wrote: > Hi, > > Using Miroslav's linuxptp-testsuite we can run a simulated HIL in github > itself. "Simulated HIL" is an oxymoron. H stand for hardware. Don't get me wrong, I absolutely love linuxptp-testsuite, and I run it on every single patch.