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>,
	Olivier Matz <olivier.matz@6wind.com>
Subject: [PATCH 6/7] cmdline: fix whitespace
Date: Mon, 16 Jan 2023 09:27:30 -0800	[thread overview]
Message-ID: <20230116172732.84976-7-stephen@networkplumber.org> (raw)
In-Reply-To: <20230116172732.84976-1-stephen@networkplumber.org>

The style standard is to use blank after keywords.
I.e "if (" not "if("

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 lib/cmdline/cmdline_rdline.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/cmdline/cmdline_rdline.c b/lib/cmdline/cmdline_rdline.c
index 5cf723a0126a..28fc54cdfebf 100644
--- a/lib/cmdline/cmdline_rdline.c
+++ b/lib/cmdline/cmdline_rdline.c
@@ -301,7 +301,7 @@ rdline_char_in(struct rdline *rdl, char c)
 		/* delete 1 char from the left */
 		case CMDLINE_KEY_BKSPACE:
 		case CMDLINE_KEY_BKSPACE2:
-			if(!cirbuf_del_tail_safe(&rdl->left)) {
+			if (!cirbuf_del_tail_safe(&rdl->left)) {
 				rdline_puts(rdl, vt100_bs);
 				display_right_buffer(rdl, 1);
 			}
@@ -354,7 +354,7 @@ rdline_char_in(struct rdline *rdl, char c)
 		/* paste contents of kill buffer to the left side of caret */
 		case CMDLINE_KEY_CTRL_Y:
 			i=0;
-			while(CIRBUF_GET_LEN(&rdl->right) + CIRBUF_GET_LEN(&rdl->left) <
+			while (CIRBUF_GET_LEN(&rdl->right) + CIRBUF_GET_LEN(&rdl->left) <
 			      RDLINE_BUF_SIZE &&
 			      i < rdl->kill_size) {
 				cirbuf_add_tail(&rdl->left, rdl->kill_buf[i]);
@@ -404,7 +404,7 @@ rdline_char_in(struct rdline *rdl, char c)
 				/* add chars */
 				if (ret == RDLINE_RES_COMPLETE) {
 					i=0;
-					while(CIRBUF_GET_LEN(&rdl->right) + CIRBUF_GET_LEN(&rdl->left) <
+					while (CIRBUF_GET_LEN(&rdl->right) + CIRBUF_GET_LEN(&rdl->left) <
 					      RDLINE_BUF_SIZE &&
 					      i < tmp_size) {
 						cirbuf_add_tail(&rdl->left, tmp_buf[i]);
-- 
2.39.0


  parent reply	other threads:[~2023-01-16 17:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 17:27 [PATCH 0/7] space after keyword cleanups Stephen Hemminger
2023-01-16 17:27 ` [PATCH 1/7] test: fix whitespace Stephen Hemminger
2023-01-16 17:27 ` [PATCH 2/7] testpmd: " Stephen Hemminger
2023-01-16 17:27 ` [PATCH 3/7] net/e1000: " Stephen Hemminger
2023-01-16 17:27 ` [PATCH 4/7] i40e: " Stephen Hemminger
2023-01-16 17:27 ` [PATCH 5/7] examples: " Stephen Hemminger
2023-01-16 17:27 ` Stephen Hemminger [this message]
2023-01-16 17:27 ` [PATCH 7/7] ip_frag: " Stephen Hemminger
2023-01-16 17:51 ` [PATCH v2 0/7] space after keyword cleanups Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 1/7] test: fix whitespace Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 2/7] testpmd: " Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 3/7] net/e1000: " Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 4/7] i40e: " Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 5/7] examples: " Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 6/7] cmdline: " Stephen Hemminger
2023-01-16 17:51   ` [PATCH v2 7/7] ip_frag: " Stephen Hemminger
2023-01-17  0:14 ` [PATCH v3 0/7] add space after keywords Stephen Hemminger
2023-01-17  0:14   ` [PATCH v3 1/7] test: fix whitespace Stephen Hemminger
2023-01-17  0:14   ` [PATCH v3 2/7] testpmd: " Stephen Hemminger
2023-01-31  8:21     ` Singh, Aman Deep
2023-01-17  0:14   ` [PATCH v3 3/7] net/e1000: " Stephen Hemminger
2023-01-17  1:21     ` Wu, Wenjun1
2023-01-17  1:26     ` Su, Simei
2023-01-17  0:14   ` [PATCH v3 4/7] i40e: " Stephen Hemminger
2023-01-17  0:26     ` Xing, Beilei
2023-01-17  0:14   ` [PATCH v3 5/7] examples: " Stephen Hemminger
2023-01-17  0:14   ` [PATCH v3 6/7] cmdline: " Stephen Hemminger
2023-01-17  0:14   ` [PATCH v3 7/7] ip_frag: " Stephen Hemminger
2023-01-22 16:00     ` Konstantin Ananyev
2023-03-12 11:28   ` [PATCH v3 0/7] add space after keywords Thomas Monjalon
2023-03-14 18:06     ` Stephen Hemminger
2023-03-14 18:17       ` 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=20230116172732.84976-7-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).