From: Jiri Pirko <jiri@resnulli.us>
To: Xabier Marquiegui <reibax@gmail.com>
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
horms@kernel.org, chrony-dev@chrony.tuxfamily.org,
mlichvar@redhat.com, ntp-lists@mattcorallo.com, shuah@kernel.org,
davem@davemloft.net, rrameshbabu@nvidia.com, alex.maftei@amd.com
Subject: Re: [PATCH net-next v2 1/3] ptp: Replace timestamp event queue with linked list
Date: Wed, 13 Sep 2023 09:56:37 +0200 [thread overview]
Message-ID: <ZQFrNRPwAl/rxoCz@nanopsycho> (raw)
In-Reply-To: <20230912220217.2008895-1-reibax@gmail.com>
Wed, Sep 13, 2023 at 12:02:15AM CEST, reibax@gmail.com wrote:
>This is the first of a set of patches to introduce linked lists to the
You are talking about a set, please introduce a cover letter and do it
there. Let the individual patch descriptions apply only for the
individual patches.
>timestamp event queue. The final goal is to be able to have multiple
>readers for the timestamp queue.
>
>On this one we maintain the original feature set, and we just introduce
>the linked lists to the data structure.
>
>Signed-off-by: Xabier Marquiegui <reibax@gmail.com>
>Suggested-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2023-09-13 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:02 [PATCH net-next v2 1/3] ptp: Replace timestamp event queue with linked list Xabier Marquiegui
2023-09-12 22:02 ` [PATCH net-next v2 2/3] ptp: support multiple timestamp event readers Xabier Marquiegui
2023-09-13 0:10 ` Vinicius Costa Gomes
2023-09-13 8:57 ` Xabier Marquiegui
2023-09-13 21:25 ` Vinicius Costa Gomes
2023-09-14 10:02 ` Xabier Marquiegui
2023-09-14 15:09 ` Richard Cochran
2023-09-14 17:12 ` Vinicius Costa Gomes
2023-09-19 15:15 ` kernel test robot
2023-09-12 22:02 ` [PATCH net-next v2 3/3] ptp: support event queue reader channel masks Xabier Marquiegui
2023-09-13 0:05 ` [PATCH net-next v2 1/3] ptp: Replace timestamp event queue with linked list Vinicius Costa Gomes
2023-09-13 7:56 ` Jiri Pirko [this message]
2023-09-14 14:21 ` Richard Cochran
2023-09-20 15:40 ` kernel test robot
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=ZQFrNRPwAl/rxoCz@nanopsycho \
--to=jiri@resnulli.us \
--cc=alex.maftei@amd.com \
--cc=chrony-dev@chrony.tuxfamily.org \
--cc=davem@davemloft.net \
--cc=horms@kernel.org \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ntp-lists@mattcorallo.com \
--cc=reibax@gmail.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=shuah@kernel.org \
/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).