From: "Tataru, AlexandruX Catalin" <alexandrux.catalin.tataru@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Troy, Rebecca" <rebecca.troy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] doc/qat: update QAT driver location
Date: Wed, 29 Jun 2022 13:14:20 +0000 [thread overview]
Message-ID: <BN6PR11MB2017BE8CBA6A8804CFA182F3B0BB9@BN6PR11MB2017.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW5PR11MB5809FB6B29E64876C18A36BFB8BB9@MW5PR11MB5809.namprd11.prod.outlook.com>
Thanks for sharing the update Roy.
Hello Rebecca,
Quick summary of the proposed updates:
1) update URL for the release notes doc 336211 v015 https://01.org/sites/default/files/downloads/336211-015-qatsoftwareforlinux-rn-hwv1.7-final.pdf
with 336211 v23 https://cdrdv2.intel.com/v1/dl/getContent/710057?explicitVersion=true
2) 01.org to be replaced by Intel Developer Zone(IDZ) for first usage. Subsequently, we can mention IDZ.
The URL for Intel QAT downloads, tech guides is developer.intel.com/quickassist
Best regards,
Catalin
-----Original Message-----
From: Zhang, Roy Fan <roy.fan.zhang@intel.com>
Sent: Wednesday, June 29, 2022 10:10 AM
To: Troy, Rebecca <rebecca.troy@intel.com>
Cc: dev@dpdk.org; Tataru, AlexandruX Catalin <alexandrux.catalin.tataru@intel.com>
Subject: RE: [PATCH] doc/qat: update QAT driver location
> -----Original Message-----
> From: Troy, Rebecca <rebecca.troy@intel.com>
> Sent: Wednesday, June 22, 2022 11:35 AM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: dev@dpdk.org; Troy, Rebecca <rebecca.troy@intel.com>
> Subject: [PATCH] doc/qat: update QAT driver location
>
> This commit removes any references to the old QAT driver location
> 01.org in the documentation and replaces them with the updated
> location intel.com.
>
> This commit also adds a note to the docs to alert users of a possible
> error when building the new QAT driver and provides the patch needed
> to resolve this error.
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-06-29 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:35 Rebecca Troy
2022-06-29 8:10 ` Zhang, Roy Fan
2022-06-29 13:14 ` Tataru, AlexandruX Catalin [this message]
2022-07-01 18:08 ` [PATCH v2] " Rebecca Troy
2022-07-01 19:11 ` [EXT] " Akhil Goyal
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=BN6PR11MB2017BE8CBA6A8804CFA182F3B0BB9@BN6PR11MB2017.namprd11.prod.outlook.com \
--to=alexandrux.catalin.tataru@intel.com \
--cc=dev@dpdk.org \
--cc=rebecca.troy@intel.com \
--cc=roy.fan.zhang@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).