24/10/2024 04:06, Ajit Khaparde: > On Tue, Oct 22, 2024 at 10:26 AM Ajit Khaparde > <ajit.khapa...@broadcom.com> wrote: > > > > On Tue, Oct 22, 2024 at 9:39 AM Stephen Hemminger > > <step...@networkplumber.org> wrote: > > > > > > On Fri, 14 Jun 2024 08:41:07 -0700 > > > Stephen Hemminger <step...@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 <step...@networkplumber.org> > > > > Reviewed-by: Somnath Kotur <somnath.ko...@broadcom.com> > Acked-by: Ajit Khaparde <ajit.khapa...@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. > > > This patch seems to have been lost/ignored. Could it be merged for 24.11. > > > > > > Note: checkpatch complaints here are incorrect. The patch is removing > > > terms master and slave, but checkpatch can't tell the difference. > > I thought it would be picked by dpdk-next-net since it looked like a > > tree-wide change. > > Since its assigned to me, I will merge it in a day or so and let the > > set take its course. I don't know why it was assigned to you. You could have re-assigned it to me.
