DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	Ruifeng Wang <ruifeng.wang@arm.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Raveendra Padasalagi <raveendra.padasalagi@broadcom.com>,
	Vikas Gupta <vikas.gupta@broadcom.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Chandubabu Namburu <chandu@amd.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>
Subject: [PATCH] doc/guides/cryptodev/features: add missing newline at eof
Date: Fri, 25 Feb 2022 10:07:34 -0800	[thread overview]
Message-ID: <20220225180734.101612-1-stephen@networkplumber.org> (raw)

Even these are ini files, they should still have new line at
end of file.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/cryptodevs/features/aesni_mb.ini | 2 +-
 doc/guides/cryptodevs/features/armv8.ini    | 2 +-
 doc/guides/cryptodevs/features/bcmfs.ini    | 2 +-
 doc/guides/cryptodevs/features/caam_jr.ini  | 2 +-
 doc/guides/cryptodevs/features/ccp.ini      | 2 +-
 doc/guides/cryptodevs/features/cn10k.ini    | 2 +-
 doc/guides/cryptodevs/features/cn9k.ini     | 2 +-
 doc/guides/cryptodevs/features/null.ini     | 2 +-
 doc/guides/cryptodevs/features/qat.ini      | 2 +-
 9 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/doc/guides/cryptodevs/features/aesni_mb.ini b/doc/guides/cryptodevs/features/aesni_mb.ini
index e616f13d504e..3c648a391ed7 100644
--- a/doc/guides/cryptodevs/features/aesni_mb.ini
+++ b/doc/guides/cryptodevs/features/aesni_mb.ini
@@ -80,4 +80,4 @@ CHACHA20-POLY1305 = Y
 ;
 [OS]
 Linux = Y
-FreeBSD = Y
\ No newline at end of file
+FreeBSD = Y
diff --git a/doc/guides/cryptodevs/features/armv8.ini b/doc/guides/cryptodevs/features/armv8.ini
index 33c1291ce6e9..ae3f7277e90b 100644
--- a/doc/guides/cryptodevs/features/armv8.ini
+++ b/doc/guides/cryptodevs/features/armv8.ini
@@ -38,4 +38,4 @@ SHA256 HMAC  = Y
 ;
 [OS]
 Linux = Y
-FreeBSD = Y
\ No newline at end of file
+FreeBSD = Y
diff --git a/doc/guides/cryptodevs/features/bcmfs.ini b/doc/guides/cryptodevs/features/bcmfs.ini
index 5def12f8a595..d8dcaee28a22 100644
--- a/doc/guides/cryptodevs/features/bcmfs.ini
+++ b/doc/guides/cryptodevs/features/bcmfs.ini
@@ -64,4 +64,4 @@ AES CCM (256)     = Y
 ;
 [OS]
 Linux = Y
-FreeBSD = Y
\ No newline at end of file
+FreeBSD = Y
diff --git a/doc/guides/cryptodevs/features/caam_jr.ini b/doc/guides/cryptodevs/features/caam_jr.ini
index ba6d10c88093..a2fe9dbba014 100644
--- a/doc/guides/cryptodevs/features/caam_jr.ini
+++ b/doc/guides/cryptodevs/features/caam_jr.ini
@@ -54,4 +54,4 @@ AES GCM (256) = Y
 ; Supported Operating systems of the 'dpaa2_sec' crypto driver.
 ;
 [OS]
-Linux = Y
\ No newline at end of file
+Linux = Y
diff --git a/doc/guides/cryptodevs/features/ccp.ini b/doc/guides/cryptodevs/features/ccp.ini
index 53abd2b68edc..0734ace9d0a6 100644
--- a/doc/guides/cryptodevs/features/ccp.ini
+++ b/doc/guides/cryptodevs/features/ccp.ini
@@ -68,4 +68,4 @@ AES GCM (256) = Y
 ; Supported Operating systems of the 'ccp' crypto driver.
 ;
 [OS]
-Linux = Y
\ No newline at end of file
+Linux = Y
diff --git a/doc/guides/cryptodevs/features/cn10k.ini b/doc/guides/cryptodevs/features/cn10k.ini
index c8193c2ccae7..166fca5adb2b 100644
--- a/doc/guides/cryptodevs/features/cn10k.ini
+++ b/doc/guides/cryptodevs/features/cn10k.ini
@@ -87,4 +87,4 @@ ECPM                    = Y
 ; Supported Operating systems of the 'cn10k' crypto driver.
 ;
 [OS]
-Linux = Y
\ No newline at end of file
+Linux = Y
diff --git a/doc/guides/cryptodevs/features/cn9k.ini b/doc/guides/cryptodevs/features/cn9k.ini
index f215ee045bb5..98ad7cf10aac 100644
--- a/doc/guides/cryptodevs/features/cn9k.ini
+++ b/doc/guides/cryptodevs/features/cn9k.ini
@@ -86,4 +86,4 @@ ECPM                    = Y
 ; Supported Operating systems of the 'cn9k' crypto driver.
 ;
 [OS]
-Linux = Y
\ No newline at end of file
+Linux = Y
diff --git a/doc/guides/cryptodevs/features/null.ini b/doc/guides/cryptodevs/features/null.ini
index ae09cdd1c018..6005fe2b8bf2 100644
--- a/doc/guides/cryptodevs/features/null.ini
+++ b/doc/guides/cryptodevs/features/null.ini
@@ -35,4 +35,4 @@ NULL = Y
 ;
 [OS]
 Linux = Y
-FreeBSD = Y
\ No newline at end of file
+FreeBSD = Y
diff --git a/doc/guides/cryptodevs/features/qat.ini b/doc/guides/cryptodevs/features/qat.ini
index bc50ecf032ca..b9755a757ef4 100644
--- a/doc/guides/cryptodevs/features/qat.ini
+++ b/doc/guides/cryptodevs/features/qat.ini
@@ -88,4 +88,4 @@ RSA						= Y
 ;
 [OS]
 Linux = Y
-FreeBSD = Y
\ No newline at end of file
+FreeBSD = Y
-- 
2.34.1


             reply	other threads:[~2022-02-25 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 18:07 Stephen Hemminger [this message]
2022-02-27 20:30 ` 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=20220225180734.101612-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=adwivedi@marvell.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=anoobj@marvell.com \
    --cc=chandu@amd.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ktejasree@marvell.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=raveendra.padasalagi@broadcom.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=ruifeng.wang@arm.com \
    --cc=vikas.gupta@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).