From: Stephen Hemminger <stephen@networkplumber.org>
To: Junfeng Guo <junfeng.guo@intel.com>
Cc: jingjing.wu@intel.com, dev@dpdk.org, omkar.maslekar@intel.com
Subject: Re: [RFC v1] raw/ntb: add support for 6th Gen Intel Xeon
Date: Mon, 7 Oct 2024 13:14:08 -0700 [thread overview]
Message-ID: <20241007131408.73e5ca8e@hermes.local> (raw)
In-Reply-To: <20231208080759.3484405-1-junfeng.guo@intel.com>
On Fri, 8 Dec 2023 16:07:59 +0800
Junfeng Guo <junfeng.guo@intel.com> wrote:
> Add support for the 6th Gen Intel Xeon Scalable processors. Note that NTB
> devices within the 6th Gen Intel Xeon compliant to PCIe 5.0 spec.
>
> Signed-off-by: Junfeng Guo <junfeng.guo@intel.com>
I would combine the 5th and 6th patches together in new version.
prev parent reply other threads:[~2024-10-07 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 7:08 [PATCH] raw/ntb: add support for 5th and " Junfeng Guo
2023-09-15 9:14 ` Wu, Jingjing
2023-09-18 2:25 ` Guo, Junfeng
2023-12-08 8:07 ` [RFC v1] raw/ntb: add support for " Junfeng Guo
2024-10-07 20:14 ` Stephen Hemminger [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=20241007131408.73e5ca8e@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=junfeng.guo@intel.com \
--cc=omkar.maslekar@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).