DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: dev@dpdk.org, akhil.goyal@nxp.com, vikram.prakash@broadcom.com,
Subject: Re: [dpdk-dev] [PATCH v1 1/1] crypto/bcmfs: fix documentation error
Date: Fri, 16 Oct 2020 12:28:27 +0200	[thread overview]
Message-ID: <12426334.BxsIZ6GtI5@thomas> (raw)
In-Reply-To: <20201016044944.22913-2-vikas.gupta@broadcom.com>

16/10/2020 06:49, Vikas Gupta:
> Fix documentation error in bcmfs.ini. Add a section for
> asymmetric algorithms.
> Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

The word "error" can be removed after "fix".

Applied, thanks

      reply	other threads:[~2020-10-16 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16  4:49 [dpdk-dev] [PATCH v1 0/1] documentation error fix Vikas Gupta
2020-10-16  4:49 ` [dpdk-dev] [PATCH v1 1/1] crypto/bcmfs: fix documentation error Vikas Gupta
2020-10-16 10:28   ` Thomas Monjalon [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12426334.BxsIZ6GtI5@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=vikas.gupta@broadcom.com \
    --cc=vikram.prakash@broadcom.com \


* 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).