From: David Marchand <david.marchand@redhat.com>
To: Yu Jiang <yux.jiang@intel.com>
Cc: dev@dpdk.org, qi.z.zhang@intel.com
Subject: Re: [PATCH V2] doc: add ice in-tree driver version for Intel NICs
Date: Wed, 19 Oct 2022 10:46:36 +0200 [thread overview]
Message-ID: <CAJFAV8yAogA85P33S+LRGXywPCZ68E+comfaXJzjKZec+rv1xw@mail.gmail.com> (raw)
In-Reply-To: <20221014071209.1501977-1-yux.jiang@intel.com>
On Fri, Oct 14, 2022 at 9:12 AM Yu Jiang <yux.jiang@intel.com> wrote:
>
> doc: add ice in-tree driver version for Intel NICs
> ice in-tree driver test starts from 22.07, cover vf-tso,vf-checksum_offload,vf-rss,
> vf-jumboframe,vm_hotplug etc.. basic vf function.
>
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>
> ---
> v2:
> - add detailed commit log
Quoting original questions:
"""
- Glad to see Intel is testing with some distribution kernels, but
what about the latest kernel?
"""
I did not get a reply on this part.
"""
- It is still unclear which features are checked / working, and which
are missing.
Having such info for this driver in the DPDK documentation would help everyone.
Do you have a list?
"""
Thanks for adding some more info in the commitlog.
Please convert this commitlog info into a documentation update (I
think doc/guides/nics/ice.rst is the right place).
This way we will have a detailed list of the supported features with
the in-tree driver, and which feature only work with the out of tree
driver.
> - correct "out-tree" to "out of tree"
This is unrelated to ice, please make this change a separate patch.
> ---
--
David Marchand
next prev parent reply other threads:[~2022-10-19 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 7:12 Yu Jiang
2022-10-19 1:51 ` Lin, Xueqin
2022-10-19 8:46 ` David Marchand [this message]
2022-10-25 2:52 ` Peng, Yuan
2022-10-25 8:23 ` David Marchand
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=CAJFAV8yAogA85P33S+LRGXywPCZ68E+comfaXJzjKZec+rv1xw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=yux.jiang@intel.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).