linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Prathu Baronia <prathubaronia2011@gmail.com>
To: prathubaronia2011@gmail.com
Cc: dan.carpenter@linaro.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	lkp@intel.com, oe-kbuild-all@lists.linux.dev,
	oe-kbuild@lists.linux.dev
Subject: [PATCH v3 2/2] axis-fifo: cleanup space issues with fops struct
Date: Thu, 18 May 2023 20:21:54 +0530	[thread overview]
Message-ID: <20230518145154.33377-2-prathubaronia2011@gmail.com> (raw)
In-Reply-To: <20230518145154.33377-1-prathubaronia2011@gmail.com>

Add required spaces for proper formatting of fops members for better
readability.

Signed-off-by: Prathu Baronia <prathubaronia2011@gmail.com>
---
 drivers/staging/axis-fifo/axis-fifo.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
index d71bdc6dd961..59e962467a3d 100644
--- a/drivers/staging/axis-fifo/axis-fifo.c
+++ b/drivers/staging/axis-fifo/axis-fifo.c
@@ -716,11 +716,11 @@ static int axis_fifo_close(struct inode *inod, struct file *f)
 }
 
 static const struct file_operations fops = {
-	.owner = THIS_MODULE,
-	.open = axis_fifo_open,
+	.owner   = THIS_MODULE,
+	.open    = axis_fifo_open,
 	.release = axis_fifo_close,
-	.read = axis_fifo_read,
-	.write = axis_fifo_write
+	.read    = axis_fifo_read,
+	.write   = axis_fifo_write
 };
 
 /* read named property from the device tree */
-- 
2.34.1


  reply	other threads:[~2023-05-18 14:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 21:40 [PATCH] axis-fifo: use devm_kasprintf for device name Prathu Baronia
2023-05-14  6:37 ` Greg Kroah-Hartman
2023-05-14 13:01   ` Prathu Baronia
2023-05-14 13:01     ` [PATCH v2 1/2] axis-fifo: use devm_kasprintf() for allocating formatted strings Prathu Baronia
2023-05-15  7:42       ` Dan Carpenter
2023-05-18 14:31         ` Prathu Baronia
2023-05-18 14:51           ` [PATCH v3 " Prathu Baronia
2023-05-18 14:51             ` Prathu Baronia [this message]
2023-05-27  7:35             ` Greg KH
2023-05-27  8:53               ` Prathu Baronia
2023-05-27 11:50                 ` [PATCH v4 1/3] axis-fifo: fix smatch warning for format specifier Prathu Baronia
2023-05-27 11:50                   ` [PATCH v4 2/3] axis-fifo: use devm_kasprintf() for allocating formatted strings Prathu Baronia
2023-05-28  9:00                     ` Greg Kroah-Hartman
2023-06-13 16:03                       ` Prathu Baronia
2023-05-27 11:51                   ` [PATCH v4 3/3] axis-fifo: cleanup space issues with fops struct Prathu Baronia
2023-05-27 22:31                     ` Uwe Kleine-König
2023-05-28  8:57                       ` Greg Kroah-Hartman
2023-06-13 16:01                         ` Prathu Baronia
2023-06-13 15:56                       ` Prathu Baronia
2023-05-28  8:59                   ` [PATCH v4 1/3] axis-fifo: fix smatch warning for format specifier Greg Kroah-Hartman
2023-06-13 16:02                     ` Prathu Baronia
2023-06-16 15:25                       ` [PATCH v5 1/2] axis-fifo: use devm_kasprintf() for allocating formatted strings Prathu Baronia
2023-06-16 15:26                         ` [PATCH v5 2/2] axis-fifo: remove the unnecessary dev_info() Prathu Baronia
2023-06-17 14:00                         ` [PATCH v5 1/2] axis-fifo: use devm_kasprintf() for allocating formatted strings Greg Kroah-Hartman
2023-06-19  6:43                           ` Prathu Baronia
2023-06-19 16:22                             ` [PATCH v6 " Prathu Baronia
2023-06-19 16:22                               ` [PATCH v6 2/2] axis-fifo: change device name by assigning unique device id Prathu Baronia
2023-06-20  5:18                               ` [PATCH v6 1/2] axis-fifo: use devm_kasprintf() for allocating formatted strings Dan Carpenter
2023-06-20  9:24                               ` Greg Kroah-Hartman
2023-05-14 13:01     ` [PATCH v2 2/2] axis-fifo: cleanup space issues with fops struct Prathu Baronia

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=20230518145154.33377-2-prathubaronia2011@gmail.com \
    --to=prathubaronia2011@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    /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).