From: Edward Cree <ecree.xilinx@gmail.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>, habetsm.xilinx@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
netdev@vger.kernel.org, Yalin Li <yalli@redhat.com>
Subject: Re: [PATCH v5 net-next 2/4] sfc: allow insertion of filters for unicast PTP
Date: Tue, 28 Mar 2023 05:09:34 +0100 [thread overview]
Message-ID: <1b5f09c6-13e5-318f-0764-83dceaf52442@gmail.com> (raw)
In-Reply-To: <20230327105755.13949-3-ihuguet@redhat.com>
On 27/03/2023 11:57, Íñ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>
> ---
Reviewed-by: Edward Cree <ecree.xilinx@gmail.com>
next prev parent reply other threads:[~2023-03-28 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 10:57 [PATCH v5 net-next 0/4] sfc: support unicast PTP Íñigo Huguet
2023-03-27 10:57 ` [PATCH v5 net-next 1/4] sfc: store PTP filters in a list Íñigo Huguet
2023-03-28 4:07 ` Edward Cree
2023-03-27 10:57 ` [PATCH v5 net-next 2/4] sfc: allow insertion of filters for unicast PTP Íñigo Huguet
2023-03-28 4:09 ` Edward Cree [this message]
2023-03-27 10:57 ` [PATCH v5 net-next 3/4] sfc: support " Íñigo Huguet
2023-03-28 4:10 ` Edward Cree
2023-03-27 10:57 ` [PATCH v5 net-next 4/4] sfc: remove expired unicast PTP filters Íñigo Huguet
2023-03-28 4:19 ` Edward Cree
2023-03-28 22:47 ` Jakub Kicinski
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=1b5f09c6-13e5-318f-0764-83dceaf52442@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).