From: Edward Cree <ecree.xilinx@gmail.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>,
habetsm.xilinx@gmail.com, richardcochran@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
Yalin Li <yalli@redhat.com>
Subject: Re: [PATCH RESEND net-next v4 1/4] sfc: store PTP filters in a list
Date: Tue, 14 Mar 2023 16:25:41 +0000 [thread overview]
Message-ID: <ff57ba46-9284-4f66-8a59-7c351960402c@gmail.com> (raw)
In-Reply-To: <20230314100925.12040-2-ihuguet@redhat.com>
On 14/03/2023 10:09, Íñigo Huguet wrote:
> Instead of using a fixed sized array for the PTP filters, use a list.
>
> This is not actually necessary at this point because the filters for
> multicast PTP are a fixed number, but this is a preparation for the
> following patches adding support for unicast PTP.
>
> To avoid confusion with the new struct type efx_ptp_rxfilter, change the
> name of some local variables from rxfilter to spec, given they're of the
> type efx_filter_spec.
>
> Reported-by: Yalin Li <yalli@redhat.com>
> Signed-off-by: Íñigo Huguet <ihuguet@redhat.com>
Reviewed-by: Edward Cree <ecree.xilinx@gmail.com>
next prev parent reply other threads:[~2023-03-14 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 10:09 [PATCH RESEND net-next v4 0/4] sfc: support unicast PTP Íñigo Huguet
2023-03-14 10:09 ` [PATCH RESEND net-next v4 1/4] sfc: store PTP filters in a list Íñigo Huguet
2023-03-14 16:25 ` Edward Cree [this message]
2023-03-14 10:09 ` [PATCH RESEND net-next v4 2/4] sfc: allow insertion of filters for unicast PTP Íñigo Huguet
2023-03-14 16:28 ` Edward Cree
2023-03-14 10:09 ` [PATCH RESEND net-next v4 3/4] sfc: support " Íñigo Huguet
2023-03-14 16:55 ` Edward Cree
2023-03-15 8:48 ` Íñigo Huguet
2023-03-15 16:14 ` Edward Cree
2023-03-14 10:09 ` [PATCH RESEND net-next v4 4/4] sfc: remove expired unicast PTP filters Íñigo Huguet
2023-03-14 17:24 ` Edward Cree
2023-03-15 8:54 ` Íñigo Huguet
2023-03-15 16:17 ` Edward Cree
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=ff57ba46-9284-4f66-8a59-7c351960402c@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=ihuguet@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=yalli@redhat.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.