From: Alessandro Marcolini <alessandromarcolini99@gmail.com>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sdf@google.com, chuck.lever@oracle.com,
lorenzo@kernel.org, jacob.e.keller@intel.com, jiri@resnulli.us,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] tools: ynl: Add sub-message and multi-attr encoding support
Date: Tue, 23 Jan 2024 01:40:15 +0100 [thread overview]
Message-ID: <1cb1ec44-cfa1-4736-ae8d-3f33df27df3d@gmail.com> (raw)
In-Reply-To: <88580D1A-7F70-4598-8E2B-18A85174EEF8@gmail.com>
On 1/22/24 22:43, Donald Hunter wrote:
> I have a longer patchset that covers this plus some refactoring for nested struct definitions and a lot of addtions to the tc spec. Do you mind if I post it and we review to see if there is anything from your patchset that is missing from mine?
>
> Thanks,
> Donald
Hi Donald,
Yes for sure, post it and we will review it together.
prev parent reply other threads:[~2024-01-23 0:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 19:19 [PATCH net-next 0/3] tools: ynl: Add sub-message and multi-attr encoding support Alessandro Marcolini
2024-01-22 19:19 ` [PATCH net-next 1/3] tools: ynl: correct typo and docstring Alessandro Marcolini
2024-01-23 16:28 ` Donald Hunter
2024-01-22 19:19 ` [PATCH net-next 2/3] doc: netlink: specs: tc: add multi-attr to tc-taprio-sched-entry Alessandro Marcolini
2024-01-23 16:35 ` Donald Hunter
2024-01-22 19:19 ` [PATCH net-next 3/3] tools: ynl: add encoding support for 'sub-message' to ynl Alessandro Marcolini
2024-01-22 19:46 ` Breno Leitao
2024-01-22 20:31 ` Alessandro Marcolini
2024-01-23 16:44 ` Donald Hunter
2024-01-24 9:12 ` Alessandro Marcolini
2024-01-24 9:45 ` Donald Hunter
2024-01-22 21:43 ` [PATCH net-next 0/3] tools: ynl: Add sub-message and multi-attr encoding support Donald Hunter
2024-01-23 0:40 ` Alessandro Marcolini [this message]
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=1cb1ec44-cfa1-4736-ae8d-3f33df27df3d@gmail.com \
--to=alessandromarcolini99@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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).