DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vikas Gupta <vikas.gupta@broadcom.com>
To: dev@dpdk.org, akhil.goyal@nxp.com, thomas@monjalon.net
Cc: vikram.prakash@broadcom.com, Vikas Gupta <vikas.gupta@broadcom.com>
Subject: [dpdk-dev] [PATCH v1 0/1] documentation error fix
Date: Fri, 16 Oct 2020 10:19:43 +0530	[thread overview]
Message-ID: <20201016044944.22913-1-vikas.gupta@broadcom.com> (raw)

Hi,
 This patch fixes documentation error in bcmfs.init

Regards,
Vikas

Vikas Gupta (1):
  crypto/bcmfs: fix documentation error

 doc/guides/cryptodevs/features/bcmfs.ini | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.17.1


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16  4:49 Vikas Gupta [this message]
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

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=20201016044944.22913-1-vikas.gupta@broadcom.com \
    --to=vikas.gupta@broadcom.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=vikram.prakash@broadcom.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).