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 2/4] sfc: allow insertion of filters for unicast PTP
Date: Tue, 14 Mar 2023 16:28:37 +0000 [thread overview]
Message-ID: <1b25b297-e427-9c83-89ee-80efc6f206eb@gmail.com> (raw)
In-Reply-To: <20230314100925.12040-3-ihuguet@redhat.com>
On 14/03/2023 10:09, Íñigo Huguet wrote:
> Add a second list for unicast filters and generalize the
> efx_ptp_insert/remove_filters functions to allow acting in any of the 2
> lists.
>
> No filters for unicast are inserted yet. That will be done in the next
> patch.
>
> The reason to use 2 different lists instead of a single one is that, in
> next patches, we will want to check if unicast filters are already added
> and if they're expired. We don't need that for multicast filters.
>
> Reported-by: Yalin Li <yalli@redhat.com>
> Signed-off-by: Íñigo Huguet <ihuguet@redhat.com>
Acked-by: Edward Cree <ecree.xilinx@gmail.com>
> -static void efx_ptp_remove_multicast_filters(struct efx_nic *efx)
> +static void efx_ptp_remove_filters(struct efx_nic *efx,
> + struct list_head *ptp_list)
Personally I'd name these something like filter_list rather than
ptp_list, but no need to respin just for that.
next prev parent reply other threads:[~2023-03-14 16:29 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
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 [this message]
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=1b25b297-e427-9c83-89ee-80efc6f206eb@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.