patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@nvidia.com>,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [19.11] doc: fix doc build after qat threshold patch
Date: Mon, 31 Aug 2020 10:12:01 +0100	[thread overview]
Message-ID: <96c619909d254b9e6fdb0c6c950ebfa740a7652d.camel@debian.org> (raw)
In-Reply-To: <BN6PR12MB12832BC1D73E4ECEDD1C8773DA510@BN6PR12MB1283.namprd12.prod.outlook.com>

On Mon, 2020-08-31 at 07:25 +0000, Ali Alnubani wrote:
> Thanks for the fix Arek.
> 
> > -----Original Message-----
> > From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > Sent: Monday, August 31, 2020 8:23 AM
> > To: bluca@debian.org; fiona.trahe@intel.com; Ali Alnubani
> > <alialnu@nvidia.com>
> > Cc: Arek Kusztal <arkadiuszx.kusztal@intel.com>; stable@dpdk.org
> > Subject: [19.11] doc: fix doc build after qat threshold patch
> > 
> > This patch fixes problem with too short underline and unexpected
> > indentation in doc build.
> > 
> > Fixes: 3cbb62874f53 ("crypto/qat: add minimum enq threshold")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> 
> Tested-by: Ali Alnubani <alialnu@nvidia.com>
> 
> Regards,
> Ali

Thanks, applied and pushed.

-- 
Kind regards,
Luca Boccassi

      reply	other threads:[~2020-08-31  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  5:22 Arek Kusztal
2020-08-31  7:25 ` Ali Alnubani
2020-08-31  9:12   ` Luca Boccassi [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=96c619909d254b9e6fdb0c6c950ebfa740a7652d.camel@debian.org \
    --to=bluca@debian.org \
    --cc=alialnu@nvidia.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=fiona.trahe@intel.com \
    --cc=stable@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).