linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wen Gu <guwen@linux.alibaba.com>
To: viro@zeniv.linux.org.uk, jlayton@kernel.org, bfields@fieldses.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	dust.li@linux.alibaba.com, tonylu@linux.alibaba.com,
	xuanzhuo@linux.alibaba.com, guwen@linux.alibaba.com
Subject: [PATCH] fasync: Use tabs instead of spaces in code indent
Date: Wed, 10 Nov 2021 14:29:16 +0800	[thread overview]
Message-ID: <1636525756-68970-1-git-send-email-guwen@linux.alibaba.com> (raw)

When I investigated about fasync_list in SMC network subsystem,
I happened to find that here uses spaces instead of tabs in code
indent and fix this by the way.

Fixes: f7347ce4ee7c ("fasync: re-organize fasync entry insertion to
allow it under a spinlock")
Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
Reviewed-by: Tony Lu <tonylu@linux.alibaba.com>
---
 fs/fcntl.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/fcntl.c b/fs/fcntl.c
index 9c6c6a3..36ba188 100644
--- a/fs/fcntl.c
+++ b/fs/fcntl.c
@@ -927,7 +927,7 @@ void fasync_free(struct fasync_struct *new)
  */
 struct fasync_struct *fasync_insert_entry(int fd, struct file *filp, struct fasync_struct **fapp, struct fasync_struct *new)
 {
-        struct fasync_struct *fa, **fp;
+	struct fasync_struct *fa, **fp;
 
 	spin_lock(&filp->f_lock);
 	spin_lock(&fasync_lock);
-- 
1.8.3.1


             reply	other threads:[~2021-11-10  6:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  6:29 Wen Gu [this message]
2021-11-10 10:58 ` [PATCH] fasync: Use tabs instead of spaces in code indent Jeff Layton
2021-11-10 11:38   ` Wen Gu

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=1636525756-68970-1-git-send-email-guwen@linux.alibaba.com \
    --to=guwen@linux.alibaba.com \
    --cc=bfields@fieldses.org \
    --cc=dust.li@linux.alibaba.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tonylu@linux.alibaba.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xuanzhuo@linux.alibaba.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).