DPDK website maintenance
 help / color / mirror / Atom feed
From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Tataru,
	AlexandruX Catalin" <alexandrux.catalin.tataru@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: RE: Website Maintenance QAT
Date: Thu, 19 May 2022 16:08:14 +0000	[thread overview]
Message-ID: <MW5PR11MB5809F9DC7741A4D9481B3F7CB8D09@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3587028.TKLx3GfHUD@thomas>

Hi Thomasz and Alex,

That's on our TODO list.

Regards,
Fan

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, May 19, 2022 5:03 PM
> To: Tataru, AlexandruX Catalin <alexandrux.catalin.tataru@intel.com>
> Cc: web@dpdk.org; Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Subject: Re: Website Maintenance QAT
> 
> 19/05/2022 10:35, Tataru, AlexandruX Catalin:
> > Hello DPDK Website maintenance team,
> >
> > My name is Alex and I am part of Intel Network Platform Group -
> QuickAssist Marketing team
> > Recently we have migrated https://01.org/intel-quickassist-
> technologyUpdate with a  new
> URL<https://www.intel.com/content/www/us/en/developer/topic-
> technology/open/quick-assist-technology/overview.html>.
> > Could we ask for your help to replace '01.org' on this 'Intel(R) QuickAssist
> (QAT) Crypto Poll Mode Driver DPDK' page
> https://doc.dpdk.org/guides/cryptodevs/qat.html  with 'Intel QAT' and add
> the new URL where necesarry?
> 
> I think you are asking to update the documentation
> which is part of the code repository and then published on the web.
> 
> Please discuss with your team to make the appropriate patch.
> 


      reply	other threads:[~2022-05-19 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  8:35 Tataru, AlexandruX Catalin
2022-05-19 16:02 ` Thomas Monjalon
2022-05-19 16:08   ` Zhang, Roy Fan [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=MW5PR11MB5809F9DC7741A4D9481B3F7CB8D09@MW5PR11MB5809.namprd11.prod.outlook.com \
    --to=roy.fan.zhang@intel.com \
    --cc=alexandrux.catalin.tataru@intel.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.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).