[PATCH v10] examples/ptp: replace terms master and slave

[Stephen Hemminger]

On Wed, 13 Nov 2024 18:33:15 +0100
Thomas Monjalon <thomas at monjalon.net> wrote:

> 24/10/2024 04:06, Ajit Khaparde:
> > On Tue, Oct 22, 2024 at 10:26 AM Ajit Khaparde
> > <ajit.khaparde at broadcom.com> wrote:  
> > >
> > > On Tue, Oct 22, 2024 at 9:39 AM Stephen Hemminger
> > > <stephen at networkplumber.org> wrote:  
> > > >
> > > > On Fri, 14 Jun 2024 08:41:07 -0700
> > > > Stephen Hemminger <stephen at networkplumber.org> wrote:
> > > >  
> > > > > Remove one of the few remaining uses of master/slave.
> > > > >
> > > > > The IEEE 1588 standard has been updated to remove the use
> > > > > of master-slave terminology. Change the sample to Use the terms
> > > > > recommended by IEEE 1588g-2022 amendment.
> > > > >
> > > > >   In place of the term “master”, use the term “timeTransmitter”.
> > > > >   In place of the term “slave”, use the term “timeReceiver”.
> > > > >
> > > > > Signed-off-by: Stephen Hemminger <stephen at networkplumber.org>
> > > > > Reviewed-by: Somnath Kotur <somnath.kotur at broadcom.com>  
> > Acked-by: Ajit Khaparde <ajit.khaparde at broadcom.com>
> > Patch applied to dpdk-next-net-brcm for-next-net branch.  
> 
> Merged in main with some rebase effort because of a new feature merged.
> I have decided to avoid camelCase and inserted a space or a hyphen
> depending on being in doc or code, in order to be consistent with our guidelines.

Ok my choice of camelCase was based on terms in current PTP spec.